Skip to content

microsoft/microsoft-azuresqldb-container

v1.0.0MIT

Develop and test applications locally with the Azure SQL Database container, including setup, secure connections, schema and data management, CI, migration from SQL Server containers, local-to-cloud workflows, APIs, and RAG.

azuresql-db-auth

Use when an app connects to the local Azure SQL Database container as sa: create a least-privilege user, choose auth per environment, keep the connection string out of source (user-secrets, Key Vault).

azuresql-db-ci

Use when CI (GitHub Actions, Azure Pipelines, GitLab) runs integration tests against the Azure SQL Database container as a service: health check, registry secrets. For Testcontainers, use azuresql-db-testing.

azuresql-db-connections

Use when hardening an app's data layer: connections drop or time out under load, add pooling and retry with backoff for transient faults, Max Pool Size. Also covers the local Azure SQL Database container.

azuresql-db-container

Use when running Azure SQL Database or any SQL/mssql container locally for dev or CI: start it, connect with sqlcmd, Podman, won't start, Entra setup. Use instead of mcr.microsoft.com/mssql/server.

azuresql-db-dab

Use when asked for an API over existing tables ('give me an API for this database', REST and GraphQL without code), or to run a local Data API builder endpoint on the Azure SQL Database container.

azuresql-db-faq

Use when asking what the local Azure SQL Database container (Private Preview) supports or why it differs from the cloud: can I back up, why USE fails, can't create a vector index, SSMS errors.

azuresql-db-feedback

Use when an azuresql-db-* skill or the Azure SQL Database container misbehaved, lacks something, or you worked around it: report a bug, file an issue, request a feature. Drafts a GitHub issue.

azuresql-db-from-sql-server

Use when a project runs mcr.microsoft.com/mssql/server in Docker or compose and local dev should behave like Azure SQL Database: switch to its container, flag SQL Server-only features.

azuresql-db-functions

Use when building a serverless CRUD API or reacting to row changes with Azure Functions on the local Azure SQL Database container: SQL bindings and trigger. For the cloud, use azure-functions-sql-bindings.

azuresql-db-import

Use when loading an existing database into the local Azure SQL Database container: import a bacpac from prod, deploy a dacpac, bring my real schema and data local with SqlPackage.

azuresql-db-local-to-cloud

Use when code built on the local Azure SQL Database container must run on Azure SQL Database: will this work in Azure, same code local and cloud, swap only the connection string, SA locally, Entra in cloud.

azuresql-db-rag

Use when storing embeddings or running similarity search, top-k or RAG on the local Azure SQL Database container with VECTOR(n) and VECTOR_DISTANCE, instead of pgvector, FAISS or a separate vector store.

azuresql-db-scaffold

Use when a new app (.NET Aspire, FastAPI, Next.js, NestJS) needs a local database: add a database, compose service, .env connection string, first migration. Uses the Azure SQL Database container.

azuresql-db-schema-migration

Use when running migrations against the local Azure SQL Database container: dotnet ef database update, prisma migrate, alembic upgrade head, a dacpac publish, so they match Azure.

azuresql-db-seed

Use when the local Azure SQL Database container needs sample data: seed the database, test or fake data, fixtures, realistic rows across related tables, bulk load a CSV for development.

azuresql-db-sidecar

Use when adding the local Azure SQL Database container to an existing docker-compose or devcontainer.json: database service, healthcheck, depends_on, app waits for the database, appdb init.

azuresql-db-testing

Use when integration tests start the Azure SQL Database container from code with Testcontainers: xUnit, Jest or pytest with a real database, per-test fixture. For CI pipelines, use azuresql-db-ci.