SQL Reporting Services - Disable or Shutdown

Question

I have a Reportins Services instance opened up in Azure.  I'm still in trial phase but trying to test it to see if it will make sense to use it after the trial ends.

I don't need a report server up and running 24h a day and it's cost prohibitive to do so anyway with my app.  However I don't see any way to turn off the instance to keep it from accruing billable usage hours when it is not being used.

Is there a way stop the server, stop the billing and fire it up for a couple hours a week when it is needed? 

Thanks,

Greg

Answer 1

For billing periods beginning after July 31, 2012, SQL Reporting will be charged for each clock hour of a reporting instance. Reporting instance hours are charged only when your service is deployed. So, in your scenario, you might be billed for all the hours when you have your subscriptions contains report servers.

For more details, see:

• http://www.windowsazure.com/en-us/pricing/details/ <Pricing Details>
• http://msdn.microsoft.com/en-us/library/windowsazure/jj156044.aspx <Accounts and Billing in Windows Azure SQL Reporting (Windows Azure SQL Reporting)>

Please let me know if this isnt clear.

Thanks

---

Chaitanya( Twitter | Blogs )

Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles.
This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 2

So is there no way to disable the reporting services instance for a few hours to avoid the charges. Turn it off when you don't need it and back on when you do, from what I can see you can only delete the SSRS subscription, and then would have to re-create it.

Answer 3

We are actively working on a new pricing model for Windows Azure SQL reporting that will better serve customers who have lower volume reporting needs. We expect to publish information on the new pricing model in the next couple weeks.  We wish to thank all of the users who provided feedback about this topic.  We’re working to address your feedback.

Evan