Database Settings Review
Use this skill for a comprehensive configuration and feature review of the current database.
Safety
- Execute read-only T-SQL only.
- Never change a database option, scoped configuration, server configuration, file, feature, or compatibility level.
- Treat inaccessible or unsupported metadata as
Unavailable. - Separate observed facts from recommendations.
- Explain benefits, risks, and workload tradeoffs before recommending any change.
Workflow
- Connect to the requested database. If none is named, retain the current database.
- Load and execute references/platform-and-database-properties.md. Stop when the platform is unsupported.
- Load and execute references/database-scoped-configurations.md. Evaluate every returned row, not only the highlighted settings.
- Load and execute references/query-store-and-automatic-tuning.md.
- Load and execute references/files-and-growth.md.
- Load and execute references/feature-and-security-inventory.md.
- For SQL Server and Azure SQL Managed Instance only, load and execute
references/server-configurations.md. Mark this section
Unavailableon Azure SQL Database. - Classify evidence using references/findings-and-recommendations.md.
- Produce the final response from references/report-template.md, preserving all twelve sections.
Required tool behavior
- Use the read-query execution tool exposed by the connected SQL provider. Prefer the SQL Tools MCP
server that ships with the
microsoft-sql-adminplugin (mssql_execute_query); otherwise another SQL tool the host provides, orsqlcmdfrom a terminal. If the SQL Tools MCP server is not connected or lists no connections, follow thesql-tools-mcp-setupskill, which asks before installing or configuring anything. - Execute queries exactly from the references after applying their platform and metadata guards.
- Do not replace a failed query with an unguarded approximation.
- Preserve permission failures as
Unavailable - insufficient permission.