About blobeater

I like MS tech, from Azure to Xbox One

Azure SQL Database and Cost Threshold for Parallelism

We all know that the magic figure for cost threshold for parallelism is 5 by default, meaning if the estimated cost of a query is greater than 5 it may very well generate a parallel plan.

Does this apply to Azure SQL Database? Let’s check.

Continue reading

Azure SQL Database – Allow Azure Services to Access Server

When you create a “logical” Azure SQL Server (I say logical because we are not really physically creating anything) there is a setting that is ticked ON by default which is called “Allow Azure services to access server”.

The question is, what does it mean? (See the highlighted section below)

Continue reading

How to setup Azure SQL Analytics

I am a big fan of this feature, I have written and spoken about it before ( https://blobeater.blog/2018/01/04/azure-sql-analytics/) but I did not cover HOW to set this up. In the previous post mentioned above all I stated was:

  • Setup a Log Analytics workspace.
  • Enable diagnostics for your SQL Databases and/or elastic pools.

Continue reading

Deleting Azure SQL Database VNETs

This is quite a new feature (currently in preview) but an important one where we now have the ability to  isolate connectivity to a database to only a given subnet or set of subnets within your VNET. This is not a theory based blog post but a practical one, setting them up is easy but deleting them via the portal is a totally different experience.

Continue reading

The world of Automatic Tuning – SQL Server 2017

Times are changing, 10 years ago I would never have thought that self-tuning databases would be available as a packaged product. I was testing out SQL Server 2017 Automatic Tuning recently and I ended up with the following situation. Below shows an image from the query store.

Continue reading

Azure Portal – Bad Request

I had a strange issue recently when trying to login to the Azure Portal. Quite simply I would enter my login details and ended up with this message – Bad Request – Request Too Long, HTTP Error 400. The Size of the request headers is too long.

Continue reading