[dba-VS] MS SQL Server Reporting Services Hosting Providers

[Gustav Brock]

Hi Shamil

I see the same pricing and can do the same calculations. But when you don't use the machine, you should shut it down to cut the costs per month.

/gustav

-----Oprindelig meddelelse-----
Fra: dba-VS [mailto:dba-vs-bounces at databaseadvisors.com] På vegne af Salakhetdinov Shamil
Sendt: 26. august 2015 21:32
Til: Development in Visual Studio <dba-vs at databaseadvisors.com>
Emne: Re: [dba-VS] MS SQL Server Reporting Services Hosting Providers

 Hi Gustav --

I checked a target AWS EC2 instance, which I wanted to test under high workload:

Windows and Web SQL Server
======================
Instance name: m4.2xlarge,
VCPU = 8,
GiB = 32.0 ,
Instance Storage --, 
I/O = High ,
EBS Opt. = Yes ,
On Demand Hourly Cost: $0.952 ,
Reserved Effective Hourly Cost: $0.516 (46%).


Do the figures look correct IYO?

If I'll use it for, say, 10 hours within 10 days (hour/day) then I will pay about 10 USD? But they also estimate monthly bill for USD696+ - if I will keep such a VPS idle but not shut-down - then the VPS hosting price promise to be around USD700/month?

Thank you.

-- Shamil


>Sunday, August 23, 2015 10:14 AM UTC from Gustav Brock <gustav at cactus.dk>:
>
>Hi Shamil
>
>I use a standard connection on port 1433 and ODBC to connect. From your network page on AWS you can control which IP addresses can gain access or select public access.
>
>I haven't worked with Reporting Services on an SQL Server so I don't know about port requirements. Should be easy to find out, though.
>
>If you wish to provide access to the reports only via a URL, you'll have to, I guess, either to have the PDF generated in advance and saved in a folder ready for download, or to have the web server of the URL to call the Reporting Service to generate the PDF and then offer it for download. The first method will be fast for the user, if the report has been generated; the second will allow for repeated calls, each time producing an updated report. In both cases I think HTTPS shouldn't raise a problem except, of course, that a trustworthy certificate must be purchased for the server. This is just thoughts - I haven't built a setup for this.
>
>/gustav