How We Handled a Vendor Retry That Loaded Twice in Snowflake
The vendor file arrived twice overnight, Snowflake loaded both copies without complaining, and finance found the problem before the pipeline did.
Add New Disk to Windows Failover Cluster for SQL Server
I have a 2-node failover cluster instance running on Windows Server 2019 Standard edition. I have a requirement to add a new SAN disk to the SQL Server failover cluster instance (FCI), and then I need to move a user database to that newly added shared disk. Can you show the steps required to add a new disk to the FCI and move the user database?
Parameter Sniffing in Production: How a 200ms Query Became a 90-Second Outage
Learn how parameter sniffing appeared in a real system and how the issues were solved.
Never ship a broken semantic model again: how to build automated tests in Power BI with user-defined functions
User-defined functions (UDFs) in Power BI let you build reusable, automated tests for your semantic models — so you catch broken measures, duplicate rows, and faulty relationships before they reach your reports. This article walks through how to use UDFs alongside PQL.Assert to standardize testing across your team, and how to automate those tests with Power Automate or a Fabric Notebook.
SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values
Learn about an alternative strategy for avoiding hardcoded literal values in SQL Server queries by using single-row views designed to mimic enum behavior.
Add Nodes to SQL Server 2022 and Windows Server 2022 Failover Cluster
I used the guide in a previous tip on Install SQL Server 2008 on a Windows Server 2008 Cluster Part 1 to install a SQL Server 2008 on a Windows Server 2008 failover cluster (WSFC). Now, I would like to upgrade and migrate my SQL Server 2008 failover clusters to SQL Server 2022 running on Windows Server 2022. What is the process for installation and configuration?
Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments
As database development scales across multiple contributors, concurrency becomes an inherent aspect of the process. Changes that are individually correct may still conflict when developed against a shifting baseline. This level introduces a disciplined approach to managing parallel changesets by controlling their scope, identifying overlap, and resolving conflicts through realignment. By ensuring that only one changeset retains its original baseline while others are adapted accordingly, deployments remain predictable and consistent. Once released, changesets are treated as immutable, and further evolution proceeds through new, forward-only changes.
Blogs
Getting the SQL Server MCP Server Running
By Steve Jones
If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...
Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations
Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...
Rambling about Data on Wheels – origins, branding, expansion
By DataOnWheels
I have been asked many times about how the name “Data on Wheels” came...
Forums
Make It Routine
Comments posted to this topic are about the item Make It Routine
DBCC CHECKDB Limits III
Comments posted to this topic are about the item DBCC CHECKDB Limits III
CROSS APPLY Fundamentals: Part 1
Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1
Question of the Day
DBCC CHECKDB Limits III
On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?
See possible answers