이 빠른 시작에서는 Quickstart 1 SQL 인증 샘플을 사용하여 SQL을 통해 DAB(Data API Builder)를 실행합니다. 사용자는 익명으로 웹앱에 액세스합니다. 웹앱은 익명으로 DAB에 액세스합니다. DAB는 SQL 인증을 사용하여 SQL Server 또는 Azure SQL 연결합니다.
샘플은 REST, GraphQL 및 MCP를 통해 SQL 데이터를 노출합니다. 또한 .NET Aspire 로컬 오케스트레이션 및 Azure 배포 스크립트가 포함됩니다.
중요합니다
SQL 인증은 설정을 단순하게 유지하지만 저장된 자격 증명을 사용합니다. 프로덕션에 포함된 비밀을 방지합니다. 로컬 비밀 정보를 .env에 저장하고, 클라우드 비밀 정보는 관리형 비밀 저장소에 저장하며, 프로덕션 워크로드에는 관리형 ID 사용을 고려하세요.
사전 요구 사항
- .NET 8 이상
- Docker Desktop
- PowerShell
- 로컬 오케스트레이션을 위한 .NET Aspire 도구
- Azure 배포를 위한 Azure CLI
- 데이터베이스 프로젝트를 배포하는 경우 sqlpackage
샘플에 표시되는 내용
- 사용자 로그인 없이 DAB를 호출하는 정적 웹앱입니다.
- DAB는 SQL을 통해 유일한 API, GraphQL 및 MCP 계층으로 구성됩니다.
- 동일한 DAB 구성에서 노출되는 REST, GraphQL 및 MCP 엔드포인트입니다.
- DAB에서 로컬의 SQL Server 및 Azure의 Azure SQL로 SQL 인증.
- 로컬 SQL Server, DAB, 웹 앱, SQL Commander 및 MCP Inspector를 위한 .NET Aspire 오케스트레이션
-
azure-infra에서 PowerShell 스크립트를 통한 Azure 배포.
인증 흐름
| 홉 | Authentication |
|---|---|
| 사용자-웹앱 | 익명 |
| 웹앱에서 API로 | 익명 |
| API에서 SQL로 로컬로 | SQL 인증 |
| Azure SQL용 API | SQL 인증 |
해당 시리즈와 비교
| Step | 변경 내용 |
|---|---|
| Previous | SQL에서 데이터 API 작성기를 사용하면 DAB CLI를 사용하여 로컬 REST 및 GraphQL 엔드포인트를 만듭니다. |
| 이 빠른 시작 | DAB-SQL 액세스에 전체 샘플 앱 및 SQL 자격 증명을 사용합니다. |
| 다음 | 관리 ID 사용 DAB의 Azure ID를 사용하여 Azure SQL 암호를 제거합니다. |
샘플 사용
샘플 리포지토리를 복제합니다.
git clone https://github.com/Azure-Samples/dab-2.0-quickstart-web_anon-api_anon-db_sql_auth.git
cd dab-2.0-quickstart-web_anon-api_anon-db_sql_auth
샘플을 로컬로 실행합니다.
dotnet tool restore
dotnet run --project aspire-apphost
Aspire 대시보드는 http://localhost:15888에서 열립니다. 웹 앱이 http://localhost:5173에서 열립니다. 대시보드를 사용하여 DAB 엔드포인트, SQL Server 컨테이너, MCP 검사기 및 SQL Commander 리소스를 검사합니다.
샘플을 Azure에 배포합니다.
pwsh ./azure-infra/azure-up.ps1
배포 스크립트는 DAB, 웹앱, MCP 검사기 및 SQL 사령관에 대한 Azure SQL 및 Azure Container Apps 리소스를 프로비전합니다.
완료되면 Azure 리소스를 정리합니다.
pwsh ./azure-infra/azure-down.ps1
키 파일
| Path | Purpose |
|---|---|
azure-infra |
Azure 배포 및 정리를 위한 Bicep 파일과 PowerShell 스크립트. |
data-api/dab-config.json |
SQL, REST, GraphQL, MCP 및 익명 엔터티 액세스에 대한 DAB 런타임 구성입니다. |
database |
SQL 데이터베이스 프로젝트, 스키마 파일 및 시드 데이터 스크립트. |
web-app |
DAB를 익명으로 호출하는 정적 웹앱입니다. |
aspire-apphost |
로컬 컨테이너 및 프로젝트 리소스를 오케스트레이션하는 .NET Aspire AppHost. |
mcp-inspector |
DAB MCP 도구를 테스트하기 위한 MCP 검사기 컨테이너 구성입니다. |
GitHub Copilot 사용하여 이 샘플 다시 생성
Visual Studio Code 샘플을 만들 작업 영역을 열고 GitHub Copilot 에이전트 모드로 전환한 다음 이 프롬프트를 붙여넣습니다.
You are GitHub Copilot running in agent mode. Recreate the Data API builder Quickstart 1 SQL Authentication sample as a complete, runnable project in the current VS Code workspace under `quickstart-01-sql-authentication`. Build a static web app, Data API builder (DAB), SQL Server locally, Azure SQL in Azure, REST, GraphQL, MCP, .NET Aspire local orchestration, SQL Commander, MCP Inspector, and Azure Container Apps deployment scripts. DAB is the only API, GraphQL, and MCP layer over SQL.
Source repository: https://github.com/Azure-Samples/dab-2.0-quickstart-web_anon-api_anon-db_sql_auth. If internet access is available, inspect or clone this repository before you create files. Reuse and adapt its files as closely as possible, especially `web-app/`, `data-api/`, `database/`, `aspire-apphost/`, `mcp-inspector/`, `azure-infra/`, scripts, and README patterns. The goal is to implement the published quickstart, not to invent a different sample. If the repository differs from this prompt or the current Data API builder docs, prefer the current docs for product behavior.
Minimize user interaction. Use the defaults in this prompt and make reasonable best guesses for noncritical choices. Do not ask for a root folder or project folder name; use the current VS Code workspace and the default subfolder. Ask only when you need approval for resource changes, secrets, permissions, materially higher cost, external account choices, or an ambiguous requirement that affects the architecture.
Start with a short plan and proceed with safe defaults before you create files or run commands. Ask only these questions if the values aren't already available from the environment or prior context:
- Which Azure subscription, primary region, fallback region, and resource group should Azure deployment use? Default fallback region: `westus2` if the primary region can't provision Azure SQL or Container Apps.
- Do you approve creating billable Azure resources if the deployment phase starts?
Use the default demo SQL Database Project unless the user asks for a simple SQL script. Generate a strong SQL password and store it only in local `.env` files or approved cloud secret stores. Use a conventional SQL admin user name such as `sqladmin` unless the target environment requires a different name.
After the answers, show a short checklist and ask for approval before implementation. Include phases for local scaffold, local validation, Azure infrastructure, Azure deployment, validation, and cleanup. Do not run any Azure command that creates or changes resources until the user explicitly approves the exact command set.
After approval, continue working without asking status-check questions. If a command, build, container, endpoint, or validation step fails, inspect the error, adjust the project, rerun the step, and continue. Keep iterating until the sample runs end-to-end or you hit a blocker that requires user action.
Use cost-first Azure defaults. Choose the cheapest option that satisfies the quickstart requirements: use a free Azure SQL database offer when the subscription and region support it; otherwise choose the lowest-cost SQL option that supports the scenario. Use Azure Container Apps consumption, minimal CPU and memory, Basic Azure Container Registry, minimal Log Analytics retention, and no always-on or dedicated plans unless required. Prioritize finishing the project. Treat regional provisioning limits as expected adjustment points, not failures: if the primary region can't provision a required service or free SQL option, use the approved fallback region such as `westus2`, and continue the deployment. Ask the user only when both the primary and fallback regions can't satisfy the requirements, when a change would materially increase cost, when a new permission is required, or when you need approval for Azure commands that create or change resources beyond the already-approved plan. Keep every resource minimal, but make the web interface neat and approachable: small code footprint, responsive layout, clear status messages, accessible labels, and simple styling that is polished rather than austere.
Verify prerequisites and report only missing items: .NET SDK, Docker Desktop running, PowerShell, Azure CLI, `sqlpackage`, .NET Aspire tooling, and the DAB CLI. If the DAB CLI is missing, install or restore it only after the user approves. Use the DAB CLI docs while building: https://learn.microsoft.com/azure/data-api-builder/command-line/.
Use these docs during implementation:
- DAB CLI reference: https://learn.microsoft.com/azure/data-api-builder/command-line/
- `dab init`: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-init
- `dab add`: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-add
- `dab validate`: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-validate
- `dab start`: https://learn.microsoft.com/azure/data-api-builder/command-line/dab-start
- DAB MCP overview: https://learn.microsoft.com/azure/data-api-builder/mcp/overview
Create this structure under the sample folder:
- `azure-infra/` for Bicep, `azure-up.ps1`, `azure-down.ps1`, and post-provision scripts.
- `data-api/` for `dab-config.json` and a DAB Dockerfile that bakes the config into the image for Azure.
- `database/` for a SQL Database Project or idempotent SQL scripts with seed data.
- `web-app/` for static HTML, CSS, and JavaScript that calls DAB anonymously.
- `aspire-apphost/` for the .NET Aspire AppHost.
- `mcp-inspector/` for MCP Inspector notes or container assets.
Handle secrets first. Add `.env`, `**/bin`, and `**/obj` to `.gitignore` before writing secrets. Use `SQL_PASSWORD` for the SQL password and `MSSQL_CONNECTION_STRING` for the DAB connection string. Never print secret values. Use `@env('MSSQL_CONNECTION_STRING')` in `dab-config.json`.
Configure DAB CORS before you start or deploy the web app. Do not leave `runtime.host.cors.origins` as `[]`. Set it to include the exact web app origins, including scheme and port: the local Aspire web origin, such as `http://localhost:5173`, and the deployed Azure Container Apps web FQDN if Azure deployment is approved. Keep `allow-credentials` set to `false` unless the sample explicitly uses browser credentials or cookies. Direct REST, GraphQL, or Swagger requests can succeed even when the browser blocks JavaScript fetch calls, so browser-origin CORS must be configured and validated separately.
Use this DAB CLI workflow and validate after each config change:
```dotnetcli
dab init --database-type mssql --connection-string "@env('MSSQL_CONNECTION_STRING')" --host-mode Development --rest.enabled true --graphql.enabled true --mcp.enabled true
dab add Todos --source dbo.Todos --source.type table --permissions "anonymous:read" --mcp.dml-tools true
dab validate --config data-api/dab-config.json
dab start --config data-api/dab-config.json
```
Use this minimal DAB runtime shape if you write the config directly:
```json
{
"$schema": "https://dataapibuilder.azureedge.net/schemas/latest/dab.draft.schema.json",
"data-source": {
"database-type": "mssql",
"connection-string": "@env('MSSQL_CONNECTION_STRING')"
},
"runtime": {
"rest": { "enabled": true, "path": "/api" },
"graphql": { "enabled": true, "path": "/graphql" },
"mcp": { "enabled": true, "path": "/mcp" },
"host": { "mode": "development", "cors": { "origins": ["http://localhost:5173"], "allow-credentials": false } }
},
"entities": {}
}
```
Use these Aspire patterns from the quickstart skills:
```csharp
var sqlServer = builder.AddSqlServer("sql-server")
.WithEnvironment("ACCEPT_EULA", "Y")
.WithDataVolume("sql-data");
var sqlDatabase = sqlServer.AddDatabase("TodoDb");
var sqlDatabaseProject = builder.AddSqlProject<Projects.database>("sql-project")
.WithReference(sqlDatabase);
var dabServer = builder.AddContainer("data-api", "azure-databases/data-api-builder", "latest")
.WithImageRegistry("mcr.microsoft.com")
.WithBindMount(new FileInfo("data-api/dab-config.json").FullName, "/App/dab-config.json", isReadOnly: true)
.WithEnvironment("MSSQL_CONNECTION_STRING", sqlDatabase)
.WithHttpEndpoint(targetPort: 5000, name: "http")
.WithHttpHealthCheck("/health")
.WaitForCompletion(sqlDatabaseProject);
```
Use `.WaitForCompletion(sqlDatabaseProject)` for DAB and SQL Commander when a SQL project deploys schema. Do not use only `.WaitFor(sqlDatabaseProject)` for a run-to-completion SQL project.
Add SQL Commander exactly enough to work. Use image `jerrynixon/sql-commander:latest`, env var `ConnectionStrings__db`, and ensure the connection string includes `TrustServerCertificate=true`.
```csharp
var sqlCommander = builder.AddContainer("sql-cmdr", "jerrynixon/sql-commander", "latest")
.WithImageRegistry("docker.io")
.WithHttpEndpoint(targetPort: 8080, name: "http")
.WithEnvironment("ConnectionStrings__db", sqlDatabase)
.WithHttpHealthCheck("/health")
.WaitForCompletion(sqlDatabaseProject);
```
Add MCP Inspector exactly enough to work with DAB MCP over HTTP. Use Streamable HTTP transport and omit auth only for local development.
```csharp
var mcpInspector = builder.AddMcpInspector("mcp-inspector")
.WithMcpServer(dabServer, transportType: McpTransportType.StreamableHttp)
.WithEnvironment("DANGEROUSLY_OMIT_AUTH", "true")
.WaitFor(dabServer);
```
Also create a VS Code MCP example for local testing:
```json
{
"servers": {
"local-dab": { "type": "http", "url": "http://localhost:5000/mcp" }
}
}
```
For Azure, bake `dab-config.json` into the DAB image. Do not rely on volume mounts in Azure Container Apps.
```dockerfile
FROM mcr.microsoft.com/azure-databases/data-api-builder:latest
COPY dab-config.json /App/dab-config.json
```
Validate before reporting success:
- `dab validate --config data-api/dab-config.json` exits with code 0.
- `dotnet run --project aspire-apphost` starts the complete local environment.
- A direct database query confirms the seeded table exists and contains rows.
- DAB `/health` returns a 2xx response.
- A browser-origin request from each web app origin receives an `Access-Control-Allow-Origin` response header that matches that origin.
- REST returns seeded rows anonymously.
- GraphQL returns seeded rows anonymously.
- MCP Inspector can list DAB tools and call `describe_entities` or an equivalent DAB MCP tool.
- SQL Commander opens from the Aspire dashboard and shows the seeded table.
- The web site returns a successful HTTP response.
- The web app displays data anonymously.
- Azure Container Apps are healthy if deployment is approved.
Do not report final URLs, asset locations, or a success summary until you directly verify database connectivity and query results, a 2xx DAB health response, and a successful web site response. This validation ensures the sample works without requiring the developer to check.
관련 콘텐츠
- 데이터 API 작성기 빠른 시작
- 빠른 시작: 데이터 API 작성기에서 관리 ID 사용
- 빠른 시작: SQL에서 데이터 API 작성기 사용
- 데이터 API 작성기에서 MCP 서버 지원
데이터 API 작성기를 Azure Container Apps - DAB 구성 파일