Display Active Slicers in Power BI using Dynamic DAX
Learn how to enhance visibility using slicers in Power BI for better report filtering and user experience.
Liability for AI Errors
Who is liable for mistakes made when listening to AI tooling? In at least one case, Steve isn't sure.
SQL ART: Who's Blocking Who? Visualising SQL Server Blocking With Spatial Geometry
Taking SQL art from shamrocks and Easter eggs to something your DBA manager might actually care about. If you've been following my SQL spatial art series — shamrocks, Easter eggs, Christmas trees — you'll know I have a habit of finding increasingly creative misuses for SQL Server's geometry data type. Most of them have been […]
The Degradation of the Turing Test
Are computers getting smart enough to pass the Turing test or are humans getting worse at representing themselves as intelligent?
How data scientists work with PostgreSQL from Python (and how to write queries that don’t break at scale)
In this article, learn how PostgreSQL powers data science workflows, including query execution, performance optimization, indexing, data retrieval, and more.
SQL Saturday Austin 2026
SQL Saturday Austin 2026 is coming on Jun 27, 2026. A free day of networking, training, and inspiration. Register today and come spend a day with your peers.
Designing Database Changes Before Deployment: Level 1 of the Stairway to Reliable Database Deployments
Stairway to Reliable Database Deployments introduces a progressive approach to managing database changes with clear intent, predictable rollback, and explicit behavioral guarantees. Starting from change design and moving toward execution and coordination in complex environments, the Stairway provides a conceptual framework for deploying database changes safely and consistently, independent of specific tools or automation platforms.
Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments
After defining the deployment contract in the previous level, this article focuses on validating a changeset before it reaches production. Rehearsal across environments ensures that execution order, rollback behavior, and baseline alignment all behave exactly as expected.
Stairway to Reliable Database Deployments Level 2 - Defining the Deployment Contract
Level 2 formalizes the behavioral guarantees that a changeset must provide in order to be safely deployed and rolled back. It introduces the deployment contract, checkpoint semantics, and the structural scope of Create and Rollback scripts. Data changes are addressed through a dedicated Update mechanism, with clear boundaries and limitations. By the end of this level, a changeset becomes a predictable and well-defined unit that can be reasoned about independently of execution context.
Stairway to Reliable Database Deployments Level 4 – Preparing for Production Deployment
This level examines how a rehearsed changeset is transformed into production-ready deployment artifacts. By consolidating scripts into controlled execution units and validating the resulting artifacts, the approach ensures that production deployment remains predictable and aligned with what was proven during rehearsal.
Blogs
Automatic Index Compaction
By ReviewMyDB
Index maintenance has always meant nightly jobs and a window you have to defend....
The Goldilocks problem – Materialized Views
I’m sure you’ve all heard the tale of Goldilocks and the Three Bears, but...
Monday Monitor Tips: Virtual Machine Usage and Cost
By Steve Jones
One of the things I’ve been requesting for a number of years is cost...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
How We Handled a Vendor Retry That Loaded Twice in Snowflake
Comments posted to this topic are about the item How We Handled a Vendor...
Cognitive Coverage
Comments posted to this topic are about the item Cognitive Coverage
Question of the Day
Getting the Average
I have this data in the dbo.Commission table in a SQL Server 2022 database.
salesperson commission Brian 12 Brian 16 Andy 7 Andy 14 Andy 21 Steve 20 Steve NULLAll the data is a varchar, and I decide to run this query to get the totals for each salesperson.
SELECT SalesPerson
, AVG(TRY_PARSE(Commission AS int)) AS TotalCommission
FROM commission
GROUP BY SalesPerson
GO
What average commission is calculated for Steve? See possible answers