data-api-builder-vscode-ext

Run SQL Commander as a companion container for browser-based SQL access, with optional Azure Container Apps configuration.

Orchestrate SQL Server and Data API Builder with .NET Aspire for local development, health-aware startup, and dashboard-driven diagnostics.

Add MCP Inspector to .NET Aspire AppHost for local SQL MCP Server validation and tool discovery.

Add SQL Commander to .NET Aspire for lightweight SQL browsing and query execution during local DAB development.

Use SQL Database Projects (.sqlproj) with .NET Aspire for declarative schema deployment via dacpac.

Deploy Data API Builder and SQL MCP Server to Azure App Service for Linux, with or without containers.

Deploy Data API Builder to Azure Container Apps with ACR, Bicep or azd, managed identity, and secure config.

Compare Azure hosting options for Data API Builder and choose ACA, App Service, ACI, AKS, local, or source hosting.

Safely use MCP Inspector with Azure-hosted SQL MCP Server endpoints for remote debugging.

Create and audit Copilot skills with strong discovery metadata, compact workflows, and explicit completion checks.

Deep guide for choosing and configuring Data API Builder authentication providers and the role/claim flow end to end.

Select a Data API Builder authentication pattern and wire roles, permissions, policies, and SQL RLS correctly.

Use Data API Builder autoentities to discover and expose database objects by pattern instead of hand-listing every entity.

Configure Data API Builder result caching across L1 in-memory, L2 distributed (Redis), and HTTP Cache-Control behavior.

Create, update, validate, and run Data API Builder projects from the terminal. Covers every dab subcommand.

Create and refine dab-config.json directly, including data-source, runtime, entities, permissions, and relationships.

Keep DAB quickstart assets consistent, runnable, and structurally compliant across local and Azure paths.

Use and customize the Data API Builder GraphQL surface, including auto-generated queries, mutations, filters, pagination, and schema naming.

Configure and operate the Data API Builder /health endpoint for runtime, data-source, and per-entity readiness checks.

Polish Data API Builder SQL MCP Server surfaces with descriptions, curated tools, and role-gated DML for reliable agent use.

Enable and control Data API Builder SQL MCP Server endpoints, client configuration, and role-safe tool exposure.

Wire Data API Builder telemetry to Application Insights, Azure Log Analytics, or any OpenTelemetry backend.

Model GraphQL relationships between Data API Builder entities, including one-to-many, many-to-one, and many-to-many via linking objects.

Design and consume Data API Builder REST endpoints, including filtering, sorting, pagination, and per-entity REST configuration.

Choose between DAB database policies and SQL Server Row-Level Security, and wire SESSION_CONTEXT claims for per-row authorization.

Run SQL Server and Data API Builder locally with Docker Compose, including optional SQL Commander and MCP Inspector services.

Use when changing VS Code launch tasks, F5 debugging, extension host testing, shared package tests, or fast single-extension validation for DAB extensions.

Use when creating a new DAB VS Code sub-extension, inferring folder names, wiring Omnibus, webpack, launch tasks, package.bat, tests, and version 1.0.0.

Use when reviewing DAB VS Code extension package size, webpack output, .vscodeignore, .gitignore, build artifacts, node_modules, VSIX contents, or dependency bloat.

Use when modifying DAB VS Code extension versions, package manifests, Omnibus extension pack entries, package.bat packaging, or marketplace release flow.

Use when refactoring DAB VS Code extensions to shared packages, reducing duplicate code, choosing dependencies, or keeping extension bundles small.