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
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers