ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #azuresqldatabase
Learn how Azure SQL Database serverless tier automatically pauses compute when idle, how to configure it via Azure CLI, and what limits and pitfalls to avoid.
Learn how to offload read‑heavy workloads from your Azure SQL primary node using Read‑Scale Out to improve write throughput and reduce CPU contention.
Pick the right Azure SQL Database tier—General Purpose, Business Critical, or Hyperscale—by balancing latency, cost, and scaling needs. A concise comparison table, trade‑off analysis, and step‑by‑step validation guide help you decide and verify your choice.
Azure SQL Database can detect plan regressions via Query Store and automatically force the last good plan. Here's how FORCE_LAST_GOOD_PLAN works, how to inspect it, and where it falls short.
Learn how to offload read-heavy queries to a secondary replica in Azure SQL Database using ApplicationIntent=ReadOnly to reduce primary node CPU and memory contention.
Parameter sniffing makes Azure SQL Database queries unstable across parameter values. Using Query Store to observe plan variance and plan forcing to lock a stable plan can provide deterministic performance without schema or code changes.
Azure SQL Database enforces a minimum TLS version for client connections and presents an X.509 certificate issued for the *.database.windows.net namespace. Client drivers such as Microsoft ODBC Driver 18 default to Encrypt=true with TrustServerCertificate=false, making certificate chain and hostname validation mandatory at connection time. The design goal is
When using Azure SQL Database to paginate a large result set with the OFFSET‑FETCH clause, you may also have Row‑Level Security (RLS) policies that filter rows before the offset is applied. The goal is to retrieve a predictable page size (e.g., 20 rows) regardless of how many rows are hidden by RLS, while keeping the query plan efficient across different off
In Azure SQL Database, least-privilege access is enforced through contained database users and database roles for both authentication methods. The design choice between token-based and password-based credential management affects how expiration events impact connection validity under pooled client usage. Microsoft Entra ID managed identities depend on short-