Offer a more scalable pricing model and increased storage capacity specifically for SQL Azure
10gb is too little for many applications, especially in multi-tenant scenarios. Going beyond 10gb currently requires a lot of work moving things around to partition one database into two or more. Adding additional partitions as the application grows becomes even more painful. Also, at $100/mo for 10gb, you're in a bad spot if your application needs 11 or 12gb.
A simple $10/mo per gigabyte, no matter how big your database is, would be a lot easier to work with.
anonymous
shared this idea
1 comment
-
TriSys commented
Numerous people have commented on this in the CTP forums - application developers should not have to worry about sharding/partitioning and other complex, unmaintainable techniques. If I procure SQL on-premise, I can use clustering to make it 100Gb and my application will run without modification. SQL Azure must be as easy to use for developers as on-premise SQL, hence it needs higher capacity than 10Gb.
