I really like the automatic tuning aspect of Azure SQL Database. This post is not a full explanation and demo. Instead, I want to point out a small point of management in the portal and your ability to configure Automatic Tuning.
Configure Automatic Tuning
You can configure Automatic Tuning within the Azure portal one of two ways. First, you can configure it with your server:
You can inherit the values from Azure, or manually define them. Regardless of your choice, if you look at the server, you can see that your automatic tuning is configured:
This is true on the server, whether I make changes to the configuration, or, just take the defaults as I did.
My confusion is on the databases. Let’s look at one:
If we look at the details, it’s clearly inherited from the server:
I am inheriting. Now, If I change the configuration, such as turning on “CREATE INDEX” on this database, after applying it, the database will again show the Automatic Tuning as being configured.
Conclusion
There’s not much to this really. I was just surprised that if I went with the defaults, it shows as being not configured. This honestly confused me. I do decide, when creating a server, what I want the automatic tuning to be, even if it’s just accepting the defaults. So, no revolutionary information today, but a confusing little bit of functionality I thought I’d share.
For those who are just getting started with Azure Automatic Tuning, I have a few posts that cover aspects of the topic, so you can reference these for a little more learning.
Hi there, I have the settings which are the exactly the same with the Azure Defaults for the SQL Fine Tuning. I would like to ask generally if these azure defaults settings as it stands the best recommendation for Azure SQL Fine Tuning, I am a website administrator for an Umbraco website that utilises this, and would advice if this is the best selected option. Thanks