azure-sql-database
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Moderate
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Windows
- Runtime requirements
- Node.js · Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: azure-sql-database
description: Expert knowledge for Azure SQL Database development including troubleshooting, best practices, d…
category: devops
runtime: Node.js / Python
---
# azure-sql-database output preview
## PART A: Task fit
- Use case: Expert knowledge for Azure SQL Database development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when choosing DTU/vCore tiers, Hyperscale, geo-replication/HA, Data Sync/sharding, or automated CI/CD deployments, and other Azure SQL Database related development tasks. Not for Azure SQL Managed Instance (use azure-sql-managed-instance), SQL Server on Azure Virtual Machines (use azure-sql-virtual-machines), Azure Cosmos DB (use azure-cosmos-db), Azure Database for PostgreSQL (use azure-database-postgresql). Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “How to Use This Skill / Category Index / Troubleshooting” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Expert knowledge for Azure SQL Database development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when choosing DTU/vCore tiers, Hyperscale, geo-replication/HA, Data Sync/sharding, or automated CI/CD deployments, and other Azure SQL Database related development tasks. Not for Azure SQL Managed Instance (use azure-sql-managed-instance), SQL Server on Azure Virtual Machines (use azure-sql-virtual-machines), Azure Cosmos DB (use azure-cosmos-db), Azure Database for PostgreSQL (use azure-database-postgresql). Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “How to Use This Skill / Category Index / Troubleshooting” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “How to Use This Skill / Category Index / Troubleshooting”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: azure-sql-database
description: Expert knowledge for Azure SQL Database development including troubleshooting, best practices, d…
category: devops
source: tomevault-io/skills-registry
---
# azure-sql-database
## When to use
- Expert knowledge for Azure SQL Database development including troubleshooting, best practices, decision making, archit…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “How to Use This Skill / Category Index / Troubleshooting” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "azure-sql-database" {
input -> user goal + target files + boundaries + acceptance criteria
context -> How to Use This Skill / Category Index / Troubleshooting
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Python | read files, write/modify files, run shell commands | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Azure SQL Database Skill
This skill provides expert guidance for Azure SQL Database. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
How to Use This Skill
IMPORTANT for Agent: This file may be large. Use the Category Index below to locate relevant sections, then use
read_filewith specific line ranges (e.g.,L136-L144) to read the sections needed for the user's question This skill requires network access to fetch documentation content. Usemcp_microsoftdocs:microsoft_docs_fetchto retrieve full articles.
- Fallback: Use the built-in
WebFetchtool if the Microsoft Learn MCP server is not available.
Category Index
| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L31-L52 | Diagnosing and fixing Azure SQL issues: performance (CPU, memory, deadlocks, blocking), capacity/log, import/export, connectivity, geo-replication, Data Sync, and Managed Instance errors. |
| Best Practices | L54-L69 | Best practices for Azure SQL operations: monitoring, auditing, security, HA/DR, failover, read replicas, maintenance, file space, Data Sync, and post-migration behavior. |
| Decision Making | L71-L93 | Guidance for choosing Azure SQL service tiers, pricing models, automation/DR options, Hyperscale choices, and migration paths (DTU↔vCore, sharding, Data Sync, Hybrid Benefit, reservations). |
| Architecture & Design Patterns | L95-L112 | Architectural patterns for Azure SQL: geo-replication, HA/DR, backups, connectivity, sharding/elastic scale-out, multi-tenant SaaS models, and rolling upgrade/failover designs. |
| Limits & Quotas | L114-L126 | Limits, quotas, and resource caps for Azure SQL (free tiers, DTU/vCore, elastic pools, Hyperscale), plus how to request quota increases and watcher/operational constraints. |
| Security | L128-L197 | Configuring Azure SQL security: auth (Entra, MFA, MI), network isolation, auditing, Defender, data protection (TDE, Always Encrypted, masking, classification), compliance, and best‑practice hardening. |
| Configuration | L199-L264 | Configuring Azure SQL databases and pools: monitoring, backups, geo-replication/failover, maintenance windows, security/immutability, scaling, elastic jobs/queries, and CLI/PowerShell/REST setup. |
| Integrations & Coding Patterns | L266-L295 | Connecting apps and tools to Azure SQL (EF Core, .NET, Node.js, Python), sharding/elastic patterns, and automating management, replication, sync, and streaming via PowerShell/Spark/Stream Analytics |
| Deployment | L297-L311 | Guides for deploying and moving Azure SQL databases: automation (GitHub, ARM, Bicep, Terraform), Hyperscale setup, regional moves, feature availability, and dev environment setup. |
Troubleshooting
Best Practices
Decision Making
Architecture & Design Patterns
Limits & Quotas
Security
Configuration
Integrations & Coding Patterns
Deployment
Source: atc-net/atc-agentic-toolkit — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review