Skip to content

Commit 4213bf9

Browse files
authored
Merge pull request #107596 from danimir/patch-1
Updating default changes announcement
2 parents d2b6ff0 + b92ecdf commit 4213bf9

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

articles/sql-database/sql-database-automatic-tuning-enable.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,13 @@ Automatic tuning can be enabled at the server or the database level through the
2828

2929
On the server level you can choose to inherit automatic tuning configuration from "Azure Defaults" or not to inherit the configuration. Azure defaults are FORCE_LAST_GOOD_PLAN is enabled, CREATE_INDEX is enabled, and DROP_INDEX is disabled.
3030

31+
> [!IMPORTANT]
32+
> As of March, 2020 changes to Azure defaults for automatic tuning will take effect as follows:
33+
>
34+
> - New Azure defaults will be FORCE_LAST_GOOD_PLAN = enabled, CREATE_INDEX = disabled, and DROP_INDEX = disabled.
35+
> - Existing servers with no automatic tuning preferences configured will be automatically configured to INHERIT the new Azure defaults. This applies to all customers currently having server settings for automatic tuning in an undefined state.
36+
> - New servers created will automatically be configured to INHERIT the new Azure defaults (unlike earlier when automatic tuning configuration was in an undefined state upon new server creation).
37+
3138
### Azure portal
3239

3340
To enable automatic tuning on Azure SQL Database logical **server**, navigate to the server in Azure portal and then select **Automatic tuning** in the menu.

0 commit comments

Comments
 (0)