Azure SQL Database Configuration
Use this skill when the user asks about Azure SQL DB configuration, service tier, edition, compute tier, MAXDOP, connection strings, or change tracking on Azure SQL Database.
Platform Guard: This skill targets Engine Edition 5 (Azure SQL DB). Not for SQL Server, MI, or Fabric SQL DB.
Required tools
- A read-only SQL query tool connected to the target server and database. Prefer, in order: the SQL
Tools MCP server that ships with the
microsoft-sql-admin plugin (mssql_list_database_connections,
mssql_connect_database, then mssql_execute_query); any other SQL tool the agent host provides for
running T-SQL and reading result sets;
sqlcmd from a terminal. If the SQL
Tools MCP server is not connected or lists no connections, follow the sql-tools-mcp-setup skill,
which asks before installing or configuring anything. If no SQL tool can be made available, give the
user the T-SQL to run and ask for the results.
- Least privilege: connect that tool with a diagnostic login that cannot write, for example one that
holds only
VIEW SERVER PERFORMANCE STATE (VIEW SERVER STATE before SQL Server 2022) or, on Azure
SQL Database, VIEW DATABASE PERFORMANCE STATE or ##MS_ServerStateReader##, plus any other read
permission these queries need. A tool is only as read-only as the login it connects with.
SQL Queries
GetSqlDbVersionSloAndEdition
SELECT
slo.service_objective AS ServiceObjective,
slo.edition AS Edition
FROM sys.databases AS d
INNER JOIN sys.database_service_objectives AS slo
ON d.database_id = slo.database_id
OPTION (MAXDOP 1);
Service Objective Interpretation
Serverless Compute Tier
Format: <service-tier>_S_<hardware-generation>_<max-vCores>
- Example:
GP_S_Gen5_2 = General Purpose serverless on Gen5 hardware, max 2 vCores
Provisioned Compute Tier
Format: <service-tier>_<hardware-generation>_<vCores>
- Example:
GP_Gen5_2 = General Purpose provisioned on Gen5 hardware, 2 vCores
Service Tiers
- GP = General Purpose
- HS = Hyperscale
Present results in this format:
### Service Objective Details
| Property | Value |
|----------|-------|
| Service objective | <value> |
| Service tier (Edition) | <value> |
| Compute tier | Serverless/Provisioned |
| Hardware | <generation> |
| vCores / Maximum vCores | <value> |
<human-like description of the SLO>
Database-Scoped MAXDOP
When the user asks about MAXDOP, retrieve the Azure SQL Database setting:
SELECT name, value
FROM sys.database_scoped_configurations
WHERE name = 'MAXDOP'
OPTION (MAXDOP 1);
- Azure SQL Database uses database-scoped MAXDOP rather than the server-scoped setting.
- A value of
0 lets the optimizer choose parallelism up to the compute resources available to the database.
- Recommend changing MAXDOP only after evaluating workload concurrency, query plans, and the database's vCore allocation.
Connection String Generation
When the user asks for a connection string:
- Retrieve SERVER_NAME, DATABASE_NAME from the current connection (
SELECT @@SERVERNAME, DB_NAME()). On Azure SQL Database, @@SERVERNAME returns the logical server name; the host name is <logical server name>.database.windows.net.
- Ask for CATEGORY (ADO.NET, JDBC, ODBC, PHP, Go) and AUTHENTICATION METHOD if not specified.
- Generate using known templates. Replace placeholders with real values where available.
- If values are missing, present the template with placeholders and note them.
Available Categories and Auth Methods
| Category |
Authentication Methods |
| ADO.NET |
Entra passwordless, SQL auth, Entra password, Entra integrated |
| JDBC |
SQL auth, Entra password, Entra integrated |
| ODBC (Node.js) |
SQL auth, Entra password, Entra integrated |
| PHP |
SQL auth |
| Go |
SQL auth |
If category/auth is not specified, present a few sample connection strings. Conclude by informing that other options are available.
Change Tracking
When asked about tracking changes in an Azure SQL Database, focus on change tracking options compatible with Azure SQL DB.
Collation Guidance
When comparing collations:
- There are both database and server default collations.
- Include information about both unless the user specifies.
- If you must choose, use the database collation but state which you chose.
- Compare database and server collation — note any differences.
1---2name: database-config-azuresql3description: "Use when the user asks to review an Azure SQL Database's configuration: service tier, service objective, compute tier, vCores, MAXDOP or connection string. For options like recovery model, use `database-settings-review`."4user-invocable: true5metadata:6 source: https://skillmd.com/skills/microsoft/database-config-azuresql7---89# Azure SQL Database Configuration1011Use this skill when the user asks about Azure SQL DB configuration, service tier, edition, compute tier, MAXDOP, connection strings, or change tracking on **Azure SQL Database**.1213> **Platform Guard**: This skill targets Engine Edition 5 (Azure SQL DB). Not for SQL Server, MI, or Fabric SQL DB.1415## Required tools1617- A read-only SQL query tool connected to the target server and database. Prefer, in order: the SQL18 Tools MCP server that ships with the `microsoft-sql-admin` plugin (`mssql_list_database_connections`,19 `mssql_connect_database`, then `mssql_execute_query`); any other SQL tool the agent host provides for20 running T-SQL and reading result sets;21 [`sqlcmd`](https://learn.microsoft.com/sql/tools/sqlcmd/sqlcmd-utility) from a terminal. If the SQL22 Tools MCP server is not connected or lists no connections, follow the `sql-tools-mcp-setup` skill,23 which asks before installing or configuring anything. If no SQL tool can be made available, give the24 user the T-SQL to run and ask for the results.25- Least privilege: connect that tool with a diagnostic login that cannot write, for example one that26 holds only `VIEW SERVER PERFORMANCE STATE` (`VIEW SERVER STATE` before SQL Server 2022) or, on Azure27 SQL Database, `VIEW DATABASE PERFORMANCE STATE` or `##MS_ServerStateReader##`, plus any other read28 permission these queries need. A tool is only as read-only as the login it connects with.2930## SQL Queries3132### GetSqlDbVersionSloAndEdition33```sql34SELECT35 slo.service_objective AS ServiceObjective,36 slo.edition AS Edition37FROM sys.databases AS d38INNER JOIN sys.database_service_objectives AS slo39 ON d.database_id = slo.database_id40 OPTION (MAXDOP 1);41```4243## Service Objective Interpretation4445### Serverless Compute Tier46Format: `<service-tier>_S_<hardware-generation>_<max-vCores>`47- Example: `GP_S_Gen5_2` = General Purpose serverless on Gen5 hardware, max 2 vCores4849### Provisioned Compute Tier50Format: `<service-tier>_<hardware-generation>_<vCores>`51- Example: `GP_Gen5_2` = General Purpose provisioned on Gen5 hardware, 2 vCores5253### Service Tiers54- GP = General Purpose55- HS = Hyperscale5657Present results in this format:5859```60### Service Objective Details61| Property | Value |62|----------|-------|63| Service objective | <value> |64| Service tier (Edition) | <value> |65| Compute tier | Serverless/Provisioned |66| Hardware | <generation> |67| vCores / Maximum vCores | <value> |6869<human-like description of the SLO>70```7172## Database-Scoped MAXDOP7374When the user asks about MAXDOP, retrieve the Azure SQL Database setting:7576```sql77SELECT name, value78FROM sys.database_scoped_configurations79WHERE name = 'MAXDOP'80OPTION (MAXDOP 1);81```8283- Azure SQL Database uses database-scoped MAXDOP rather than the server-scoped setting.84- A value of `0` lets the optimizer choose parallelism up to the compute resources available to the database.85- Recommend changing MAXDOP only after evaluating workload concurrency, query plans, and the database's vCore allocation.8687## Connection String Generation8889When the user asks for a connection string:90911. **Retrieve** SERVER_NAME, DATABASE_NAME from the current connection (`SELECT @@SERVERNAME, DB_NAME()`). On Azure SQL Database, `@@SERVERNAME` returns the logical server name; the host name is `<logical server name>.database.windows.net`.922. **Ask** for CATEGORY (ADO.NET, JDBC, ODBC, PHP, Go) and AUTHENTICATION METHOD if not specified.933. **Generate** using known templates. Replace placeholders with real values where available.944. If values are missing, present the template with placeholders and note them.9596### Available Categories and Auth Methods9798| Category | Authentication Methods |99|----------|----------------------|100| ADO.NET | Entra passwordless, SQL auth, Entra password, Entra integrated |101| JDBC | SQL auth, Entra password, Entra integrated |102| ODBC (Node.js) | SQL auth, Entra password, Entra integrated |103| PHP | SQL auth |104| Go | SQL auth |105106If category/auth is not specified, present a few sample connection strings. Conclude by informing that other options are available.107108## Change Tracking109110When asked about tracking changes in an Azure SQL Database, focus on change tracking options **compatible with Azure SQL DB**.111112## Collation Guidance113114When comparing collations:1151. There are both **database** and **server** default collations.1162. Include information about both unless the user specifies.1173. If you must choose, use the **database** collation but state which you chose.1184. Compare database and server collation — note any differences.