Articles

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.

2008-07-28

7,924 reads

Blogs

Three Ways to Use Snowflake Data in Microsoft Fabric

By

Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...

Deploying an Updated Model with SQL Compare 16

By

In a previous post, I deployed a model to a database using SQL Compare...

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Read the latest Blogs

Forums

Automating Database Cleanup for PostgreSQL Using Python

By sabyda

Comments posted to this topic are about the item Automating Database Cleanup for PostgreSQL...

The Query Optimizer and Page Density

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Query Optimizer and Page...

There Are a Lot of Databases

By Steve Jones - SSC Editor

Comments posted to this topic are about the item There Are a Lot of...

Visit the forum

Question of the Day

The Query Optimizer and Page Density

If I have a fillfactor set to 70%, this reduces my page density to roughly 70%. Does this affect the query plans that the optimizer chooses?

See possible answers