The infamous setting that we all know and love – MAXDOP. Did you know that you can actually control MAXDOP when using Azure SQL Database? You might not be able to tinker with the Cost Threshold for Parallelism setting but you sure can with MAXDOP.
So you want to do a clean-up exercise in Azure and remove some databases. You go to delete a database that is no longer required (as shown below).
You may (or may not) have a requirement to setup a linked server to Azure SQL Database from a locally installed SQL Server. One reason could be to pull down some reports from an Azure SQL Database to a local file share. Whatever your reason is hopefully you will find this blog post useful because I ran into some complications on the way.
Back in September 2017 Microsoft announced a new security feature for Azure SQL Database called the SQL Vulnerability Assessment (VA). It is currently in preview mode where it has the ability to find, you can guess, security based vulnerabilities for your database such as misconfigurations, excessive permissions, and exposed sensitive data.
Let’s setup a scan. You can find this feature within the settings section of your database.
Naturally the cost of Azure SQL Database directly relates to what tier and performance level you are using. Starting from the least expensive basic database to the more premium ones I thought it would be worthwhile capturing the costs (GBP) across all tiers.
Let’s start off with a quick overview of SQL Server versions and compatibility levels.
- 100 = SQL Server 2008 and Azure SQL Database
- 110 = SQL Server 2012 and Azure SQL Database
- 120 = SQL Server 2014 and Azure SQL Database
- 130 = SQL Server 2016 and Azure SQL Database
- 140 = SQL Server 2017 and Azure SQL Database
So with SQL Server 2017 now available to the public what level is a newly created Azure SQL Database set at?
Things go wrong in IT, it is no different with the cloud. When I say cloud I am thinking quite specific such as the underlying infrastructure that a company like Microsoft looks after for their Azure platform.
If you remember last month I wrote about DBCC CHECKDB and Azure SQL Database, more specifically whose responsibility (Microsoft’s) it is and ponderings on how it is actually done. (https://blobeater.blog/2017/09/04/dbcc-checkdb-azure-sql-database/)
You have the ability to actually pause SQL Server, if you are in SQL Server Management Studio (SSMS), you might have noticed it as the below image.