Skip to main content

Creating an Azure SQL Database

By David Postlethwaite

Once you have logged in to the Azure Management Portal you can start to  create an Azure SQL Database.
Azure SQL Database is an example of Platform as a Service (PaaS), we don’t have to build a Windows server or install the SQL software or configure the SQL instance. We don’t have to worry about software upgrades or the disc configuration Microsoft have done all of that for us. Azure simply provides us with a platform where we can place our data.Once we have created a database we can connect to it from our pc using SQL Server Management Studio or connect our applications to the database by using ADO or ODBC.

From the management console click on the database icon image   on the left hand side of the screen then select +New from the grey section at the bottom.

image

We have the option of quick create, custom create or import.
Quick Create just asks for a database name and a server put it on and it then creates a standard database. You can then configure the size and performance level afterwards from the Management Portal.
Otherwise use Custom Create so you can also configure the size and performance level at the same time.

image

It usually takes less than a minute for the system to create the database for you.
The import option allows you can load a special type of backup file called a BACPAC file from Azure blob storage which we will discuss in a later article.
An Azure SQL database must be placed on an Azure SQL server. This server is simply a container to place your databases. There is very little that can be configured for a server other than its location. Importantly an Azure SQL server can host a maximum of 150 databases and has a maximum amount of power available to it (2000 DTUs which we’ll discuss in a later article)

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…