External Article

The Myth of Over-Normalization

Too often, denormalization is suggested as the first thing to consider when tackling query performance problems. It is said to be a necessary compromise to be made when a rigorous logical design hits an inadequate database system. As the saying goes, “Normalize ‘til it hurts, then denormalize ‘til it works”. In reality, Denormalization always leads eventually to tears.

Blogs

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

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

By

I am excited to host T-SQL Tuesday for the first time. I want to...

Read the latest Blogs

Forums

Practical Ways to Approach SQL Server Problems and Case Studies

By academicexpertt

Working with SQL Server can involve more than just writing queries. Understanding database design,...

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Importing Excel files into SQL Server using DuckDB and Python

By Cláudio Tereso

Comments posted to this topic are about the item Importing Excel files into SQL...

Visit the forum

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