Skip to main content

Microsoft Azure SQL Databases – Power and Performance

By David Postlethwaite
On the Database Scale page we can decide on the performance level that we want our database to have.
There are three performance levels Basic, Standard and Premium
  • Basic is best suited for a small size database, supporting one single operation at a time such as for development or testing, or small scale infrequently used applications.
  • Standard is the best option for most cloud applications, supporting multiple concurrent queries such as workgroup or web applications.
  • Premium is designed for high transactional volume, supporting a large number of concurrent users and requiring the highest level of business continuity such as mission critical applications.

There used to be two types called Web and Business they have now been retired but you’ll still find them mentioned in the documentation and it is still possible through SSMS to create a web level database. (Upgrade SSMS 2014 to CU5 to get the latest) They are due to be removed in September 2015.
Unlike your traditional on premises database server you cannot choose the number of CPUs, amount of memory or disc configuration with SQL Azure DB.
Each Service tier has different Power levels which are measured in Database Throughput Units or DTUs. A DTU represents the power of the database engine as a mix of CPU, memory and read and write rates.
Micrsoft Azure SQL Databases - Service Tiers
The table below show you the power levels available for each tier. Expect these to increase over the coming months and years.
The idea of a DTU is to show relative power that there is between the different levels So S1 will give you 4 times the power of Basic and P1 is 10 times more powerful than S0.
To give you some idea of what you might expect from each level Microsoft have published a benchmark transaction rate.
Bennch Mark Transaction Rate
You decide on the power level you think you require and then monitor and tune the database as required. It is very easy to change from one tier to another if you decide you need more or less power but changing the level will cause the database to stop and restart. Remember, each server can have a maximum of 150 databases and a maximum of 2000 DTUs

Visit our SQL Server and Azure Consulting page

Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…