SQL Server Insights from Production Environments

Practical observations and approaches from real-world SQL Server environments.

SQL Server in the Real World

SQL Server rarely becomes difficult because of one configuration setting or one badly written query. Problems usually emerge from the interaction between workload, architecture, infrastructure, configuration, and decisions that have accumulated over time.

This is where the articles on CraftedSQL start. They are based on practical experience from production environments and focus on understanding what is actually happening inside SQL Server before changing anything. Topics range from performance troubleshooting and query behavior to high availability, security, migrations, upgrades, and day-to-day database operations.

The goal is not to collect generic best practices. It is to explain how SQL Server behaves in real environments, why seemingly reasonable decisions sometimes create problems later, and how those situations can be analyzed systematically.

What You'll Find Here

Performance & Troubleshooting

Slow queries, blocking, resource pressure, execution behavior, workload-related problems, and the process of finding the actual root cause.

Architecture & Operations

High availability, migrations, upgrades, patching, infrastructure decisions, and the operational details that determine whether systems remain stable and maintainable.

Security & Reliability

Permissions, access patterns, configuration, operational safeguards, and the technical decisions that can turn into larger risks over time.

Latest SQL Server Articles

Busy highway interchange as a metaphor for SQL Server execution plans and runtime context

SQL Server Execution Plans Need Runtime Context

SQL Server execution plans are often the first place I look when a query behaves differently from what I would expect. They tell me how SQL Server chose to access the data, which join strategies it selected and where estimates may not match what actually happened during execution. An actual ...
Azure Arc SQL Server visibility across an existing hybrid SQL Server estate

Azure Arc-enabled SQL Server: Visibility Before Migration

Azure Arc SQL Server can be useful long before an organization decides to move a database anywhere. In many SQL Server environments, there is an earlier problem to solve: before anyone makes a sensible decision about migration, consolidation or platform strategy, somebody needs to understand what is already there. That ...
Suspension bridge leading through a mountain landscape, representing SQL Server restore validation and service recovery

A Restored Database Is Not the Same as a Recovered Service

A SQL Server restore can complete successfully while the business service behind it remains unavailable. The database may return to an ONLINE state, but that status only tells us something about SQL Server itself. SQL Server restore validation therefore needs to look further: can the application connect, are the required ...
Technician reviewing existing wiring before changes, representing historical SQL Server permissions and dependencies

When Permissions Outlive Their Context in SQL Server

Most SQL Server permissions begin with a perfectly reasonable decision. An application needs access to another database, a service account requires additional rights for a deployment, or an administrator receives broader permissions while a migration is in progress. At that point, the reason is probably known, and there may even ...
Railway junction representing SQL Server workload placement across on-premises, Azure and hybrid platform options.

Why Workload Placement Matters More Than the Platform Label for SQL Server

When companies start discussing SQL Server workload placement, the conversation often begins with the platform. Should the workload move to Azure? Would Azure SQL Managed Instance be a better fit? Should the database stay on-premises for another few years, or would that simply postpone an inevitable migration? Those are reasonable ...
Engineer inspecting industrial equipment with a clipboard during a technical review, representing structured assessment and operational risk evaluation.

SQL Server Health Checks: Small Operational Gaps That Become Expensive Later

A SQL Server environment can run reliably for years while operational gaps remain unnoticed. A structured Health Check helps identify which findings matter, understand their consequences and set meaningful priorities.
Engineer measuring a precision component at a technical workstation, illustrating production readiness for SQL Server vector search.

SQL Server Vector Search: What to Evaluate Before Production

SQL Server 2025 adds native support for vector data and vector search. Applications can keep embeddings alongside relational data and use the SQL Database Engine to find semantically similar information. A small proof of concept is easy enough to build: store an embedding, calculate the distance between vectors and return ...
Operations control room used as a visual for historical SQL Server performance analysis

SQL Server Query Store: Why Performance History Matters

A SQL Server performance problem is not always still there when someone finally has time to investigate it. SQL Server Query Store becomes especially useful when the system has already returned to normal. Users may report that an application was slow around 10:00. An hour later, response times are back ...
SQL Server backup strategy represented by labeled backup media stored in organized archive racks

SQL Server Backup Strategy: Why Successful Backups Are Not Enough

Most SQL Server environments have a backup process, but not every SQL Server backup strategy reflects actual recovery requirements. Teams may run jobs according to a defined schedule, monitor successful completion and retain the files for a specified period. Recovery readiness means that the organization can restore the required databases ...
Industrial barriers in a technical tunnel representing a SQL Server blocking chain and head blocker.

SQL Server Blocking: What the Head Blocker Does Not Tell You

A SQL Server blocking chain shows which session is holding up other work. It does not explain why the transaction remained open long enough to affect production.

Facing SQL Server performance issues?

Whether you're dealing with a performance issue, planning an upgrade, or reviewing your SQL Server architecture, let's start with a conversation.

Start a Conversation