Azure SQL Database new performance level
A new performance level for Azure SQL Database was recently announced, called P15. This new offering is more than two times more powerful than the next best offering, P11. P15 offers 4000 database transaction units (DTU) where P11 offered 1750 DTU’s. Also, the max concurrent workers and concurrent logins increased from 2,400 to 6,400; the max concurrent sessions stayed the same at 32,000; and the max In-memory OLTP storage increased from 14GB to 32GB.
More info:
Azure SQL Database new premium performance level P15 generally available
James, thanks for your site and info. I’ve been doing major SQL Server systems for a while, but have yet to lay hands on Azure. Here’s a challenge we may need to deal with. Say we have a web site and we put up a new game/product and expect to be hit with say 1m responses in the first minute. OK we need to queue them up, but we also want to process them ASAP. In Azure, where will the bottlenecks be? Presume it is not logins, nor sessions, nor even worker threads, but locking and blocking on transaction tables, maybe tempdb, maybe log. On SQL Server I know how to estimate these, on Azure not so much. The promise of Cloud is that we can scale to handle peaks – but is this too peaky? Appreciate any thoughts on the matter. Thanks.
For that many transactions I would look at using DocumentDB.
>DocumentDB (Azure NoSQL “blazing fast”)
An interesting option, that I see I need to research further, thanks. Have you used this yet, in an application that requires the blazing speed?
Also, if I may, I’d like to add a follow-up question (of the kind we’re apparently not supposed to ask) back on the Azure SQL DB side: approximately (or exactly) how many cores does one get, in a P15 account?
Thanks.