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

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Designing a Storage Load Test for SQL Server

By

I’ve been doing storage load tests for SQL Server for a long time, both...

Read the latest Blogs

Forums

A question about how to store the address in the database

By eichnerm

I have an app that has an address field on the customer and the...

SSIS package failing intermittently on last Excel Component

By Reh23

Good Afternoon, I have a Job which "fires" off an SSIS package (that is...

T-SQL in SQL Server 2025: JSON_ARRAYAGG

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

Question of the Day

Multiple Sequence Values

How do I easily get the next 12 sequence values from a sequence object?

See possible answers