microsoft/microsoft-sql-vscode
Build and manage Azure SQL Database applications in Visual Studio Code with the MSSQL extension, including connections, schema and ORM workflows, deployment, diagnostics, security, data movement, recovery, T-SQL, vector search, and database projects. Data API Builder configuration guidance is excluded where it would duplicate tools provided by the extension; hosting Data API Builder in Azure and connecting remote MCP clients are included.
Use when a login fails (18456, 'Login failed for user'), a user can't open a database, a permission is denied, or an Entra or managed identity login fails. For network errors, use connectivity-troubleshoot.
Use when wiring Azure Functions to Azure SQL Database: a serverless CRUD API with SQL input or output bindings, SqlTrigger on row changes, a SQL trigger that never fires, an output binding that updated instead of inserting.
Use when loading a large file or many rows into an Azure SQL Database table fast: bulk insert a CSV, bcp, SqlBulkCopy, fast_executemany, BULK INSERT or OPENROWSET refusing a local file (Msg 12713), LOG_RATE_GOVERNOR.
Use when queries hang right now: who is blocking, the head blocker, why a blocking DMV looks empty. Has tested queries and rules common answers miss, e.g. a sleeping head blocker is absent from sys.dm_exec_requests. For past blocking, use read-only blocking root-cause investigation using the host SQL tools.
Use when connecting a .NET app to Azure SQL Database with Microsoft.Data.SqlClient: packages, connection string, pooling, managed identity or Active Directory Default failing. For EF Core, use ef-core-azure-sql.
Use when connecting Python to Azure SQL Database: mssql-python or pyodbc, the ODBC driver, 'data source name not found', driver missing in a container image, Entra tokens. For SQLAlchemy, use sqlalchemy-azure-sql.
Use when connecting Node.js or TypeScript to Azure SQL Database with mssql: pool setup, an API slowing or out of connections under load, passwordless Entra ID, typed results. For Prisma, use prisma-azure-sql.
Use when connecting an app to Azure SQL Database: which driver, what goes in the connection string, retry, a first connection that fails then works (40613), certificate errors or TrustServerCertificate.
Use when a client can't connect or gets a connection error (timeout, 53/10060/10061, SQLSTATE 08001, TLS, firewall 'IP not allowed', 4060). For login or permission issues, use authentication-diagnostics.
Use when the user wants an Extended Events session to capture slow queries, deadlocks or blocking over hours or days, or an XE ring buffer stays empty. To explain a captured deadlock, use read-only SQL Server deadlock graph analysis using the host SQL tools.
Use when connecting an AI agent to a hosted Data API builder MCP endpoint, writing its server description, making its tools read-only, or diagnosing role, tool, permission or session failures, including describe_entities reporting 'no entities configured' for a configured endpoint.
Use when the user asks about deadlocks, deadlock history or prevention on Azure SQL Database or Fabric SQL Database. For SQL Server, Managed Instance or a supplied deadlock XML, use read-only SQL Server deadlock graph analysis using the host SQL tools.
Use when deploying an app and its Azure SQL Database with azd: azd up, which template to start from, no password in the deployment, or deploy succeeded but the first database call fails to log in.
Use when deploying Data API builder to Azure Container Apps, or a deployed DAB app shows identity, health (403), host (MCP 403), scaling or startup failures.
Use when creating, reviewing or porting tables for Azure SQL Database: key and string lengths, collation, identity gaps. Has verified behavior common answers miss, e.g. a unique index on nvarchar(1000) builds with only a warning.
Use when starting from the microsoft/azuresql-devcontainers templates (.NET, Aspire, Node, Python) or they misbehave: empty database, schema not deployed, behaviour unlike Azure docs. Their database is SQL Server.
Use when EF Core targets Azure SQL Database: EnableRetryOnFailure, 'does not support user-initiated transactions', duplicate rows after a retry, UseAzureSql or UseSqlServer, AsSplitQuery, JSON columns.
Use when generating embeddings in Azure SQL Database or reviewing that setup: CREATE EXTERNAL MODEL, AI_GENERATE_EMBEDDINGS, Azure OpenAI from T-SQL. Has verified behavior common answers miss, e.g. the model DDL succeeds with a credential that can never work.
Use when setting up passwordless Microsoft Entra ID or managed identity access to Azure SQL Database or the container (CREATE USER FROM EXTERNAL PROVIDER), or it fails: Msg 33134, 18456 login failed, 4060.
Use when deploying schema to Azure SQL Database from GitHub Actions: azure/sql-action, dacpac publish, OIDC with no stored password, login failing after adding an environment, client IP or firewall errors.
Use when CPU is high on SQL Server or Azure SQL (alerts, throttling, SOS_SCHEDULER_YIELD waits) and the user wants the queries responsible. For a broad resource snapshot, use resource-usage-sqlserver.
Use when data-file reads are slow or heavy: PAGEIOLATCH waits, high read latency, many physical reads, Azure SQL data IO throttling. For WRITELOG or log latency, use investigate-sql-log-io-pressure.
Use when commits are slow or log writes lag: WRITELOG waits, high log write percent, log throughput throttling, too many VLFs. For PAGEIOLATCH or data-file reads, use investigate-sql-data-io-pressure.
Use when queries wait on memory grants (RESOURCE_SEMAPHORE), spill to tempdb, hit out-of-memory errors (701, 802, 8645), or PLE drops. For a broad resource snapshot, use resource-usage-sqlserver.
Use when using LangChain or LlamaIndex with Azure SQL Database: SQL agent or text-to-SQL emits LIMIT, read-only agent, SQLDatabaseToolkit, langchain-sqlserver vector store, vector index refused.
Use when writing or reviewing dynamic SQL on Azure SQL Database for injection: sp_executesql vs EXEC, dynamic ORDER BY or table names. Has verified behavior common answers miss, e.g. QUOTENAME returns NULL past 128 characters.
Use when using Prisma with Azure SQL Database: schema.prisma, prisma migrate failing in Azure (P3020, shadow database), no Json type or enums, url unsupported in Prisma 7, driver adapter.
Use when creating an Azure SQL Database: a free SQL database in Azure, provision SQL for this app, give me a connection string, firewall rule, Entra-only admin, or created but nothing connects.
Use when choosing or moving to Hyperscale in Azure SQL Database: should I use Hyperscale, convert or move back, near 4 TB, vCores, serverless, read replicas, outgrowing the free offer.
Use when building a RAG pipeline end to end on Azure SQL Database: chat with my documents, semantic search over my data, keep embeddings in sync, answers worse after switching models, other tenants' chunks returned.
Use when reading an Azure SQL Database execution plan: what is expensive, why a scan, actual vs estimated rows, warnings, missing-index hints, getting the actual plan, a plan returned as NULL.
Use when many queries time out under load, or SQL Server or Azure SQL is slow overall and it's unclear whether CPU, memory, IO, TempDB or disk is the cause. For one slow query, use slow-query-investigation.
Use when Azure SQL Database data is lost: restore to before a bad deployment, a dropped table or database, point-in-time restore, geo-restore, long-term retention, RESTORE DATABASE refused.
Use when isolating tenants in a shared Azure SQL Database or checking isolation: row level security, SESSION_CONTEXT, rows leaking or vanishing. Has verified behavior common answers miss, e.g. a filter predicate alone lets a tenant write into another.
Use when asking if a schema change is safe on a live Azure SQL Database: add or alter a column, NOT NULL, deploys timing out, rollback. Has verified behavior common answers miss, e.g. a NEWID() default rewrites the table; a constant one doesn't.
Use when a Microsoft SQL skill, plugin or marketplace was wrong: bad steps, wrong skill fired, install failed, or you worked around it. Files a redacted bug report. The azuresql-db-* skills have their own feedback skill.
Use when one specific query got slow, changed plans, or swings from seconds to minutes with the same parameters. Has tested queries and rules common answers miss, e.g. Query Store averages need execution weighting. For many slow queries, use resource-usage-sqlserver.
Use when building or publishing a SQL database project (.sqlproj, dacpac) for Azure SQL Database: build passes but publish fails, a renamed column lost data, deployment scripts, target platform.
Use when using SQLAlchemy or Alembic with Azure SQL Database: mssql+pyodbc URL, insert fails on a table with a trigger (OUTPUT clause), fast_executemany no faster, implicit_returning.
Use when moving a whole Azure SQL Database as a file with SqlPackage: export or import a bacpac, extract or publish a dacpac, copy between servers, dacpac vs bacpac, SQL71627 or SQL71659 failures.
Use when writing, porting or reviewing T-SQL for Azure SQL Database, or results look wrong with no error: NULLs, NOT IN, integer division. Has verified behavior common answers miss, e.g. the 'NULL eliminated' warning never reaches sqlcmd.
Use when storing, querying or reviewing JSON in Azure SQL Database: json type or nvarchar(max), OPENJSON, JSON_VALUE returning NULL. Has verified behavior common answers miss, e.g. nvarchar(max) silently stores invalid JSON.
Use when writing or reviewing an upsert or MERGE for Azure SQL Database: insert or update, ON CONFLICT, lost writes or 2627 under load. Has verified behavior common answers miss, e.g. a bare MERGE loses writes under concurrency.
Use when writing, reviewing or debugging vector search on Azure SQL Database: VECTOR_DISTANCE, VECTOR_SEARCH, vector index. Has verified behavior common answers miss, e.g. ORDER BY VECTOR_DISTANCE never uses the index. For RAG, use rag-on-azure-sql.