THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

Windows Azure SQL Reporting - Great to see a dramatic price decrease for lower volume users

Published Friday, December 21, 2012 1:26 PM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Mahesh C said:

Greg, this is really good news. A lot of clients throw up their hands when they hear the current pricing. The new pricing is much more palatable.

Thanx, Mahesh

December 21, 2012 6:35 AM
 

Rob M. said:

What is the scale up factor? Is it not $0.16 for each additional 30 reports per hour? Or is there a big jump at 31 reports to the old pricing model?

December 21, 2012 1:18 PM
 

Greg Low said:

Looks like the scale up factor works the same way as before but now 16 cents per 30 reports within an hour.

Yep, it's still not where I think it needs to be but dramatically better than before.

December 26, 2012 9:05 PM
 

Donna Kelly said:

I would echo the previous posters . . . this pricing model is nuts.

One of the big pluses of Azure is very fast provisioning of micro-developments to respond to specific business needs right [i]now[/i].   Part of doing that is to provision a reports server quickly, even knowing it won't get used very much.

The pricing model for Azure SQL Database is brilliant . . . I can create a little SQL Database and upload it via SSDT the same day.  (Haven't got a good fast solution for online data entry yet, though, any ideas?)

But the Reporting guys have gone squirrely!  The pricing model of $/provisioned hour kills the whole concept of Azure SQL Reporting from little systems stone-dead.

Cheers,

Donna Kelly

December 27, 2012 6:16 AM
 

DavidM said:

the new pricing works for most high utilization scenarios too, you will simply pay a lot less for idle time. even high utilization scenarios have some idle time (middle of the night, weekends etc.) so the payment would be reduced significantly for these as well.

December 27, 2012 7:22 AM
 

JonM said:

Why not have a per report or per page pricing model or something?  I don't think per hour works with Reporting Service Azure. I think the reporting services model needs to be rethought to support this.  Essentially I just want a on-demand service that I send a report definition into (along with the datasources) and get a report back in the format I want.  Right?  Couldn't MS just wrap the existing renderer classes for this?

January 17, 2013 11:20 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Tags

No tags have been created or used yet.

Archives

Privacy Statement