External Article

Testing before coding: shifting farther left

A term I have only recently learned is "shift left testing." You can read more about this on Wikipedia here. The term was coined in 2001 and generally means testing earlier in the development lifecycle. Hence, shifting your testing left in the timeline. Just how left should you shift your testing, though? In my mind, so early, the rooster hasn't entirely fallen asleep yet.

SQLServerCentral Editorial

The Top 5 Technologists

There's a common party question about which 5 people would you invite to a dinner party? Often this is amended to include living or dead people, and it's often interesting to hear people tell you who they'd invite and why. Since most of the people reading this work in technology in some way, I was […]

Blogs

The Mystery of SQL Server 2025’s New Tricks – Scooby Dooing Episode 5

By

Every Scooby-Doo mystery starts with a haunted house, a strange villain, and a trail...

A Prompt AI Experiment

By

Prompt AI released recently and I decided to try a few things with the...

SQL Server Is Slow (part 1 of 4)

By

How should you respond when you get the dreaded Email/Slack/Text/DriveBy from someone yelling at...

Read the latest Blogs

Forums

how to get notification that my database has corssed 8gb

By rajemessage 14195

i have sqlexpress on rds, is there any way i can get notifacation that...

SQL Server, Heaps and Fragmentation

By dbakevlar

Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation

Stairway to Azure SQL Hyperscale – Level 2: Page Server Architecture Explained

By Chandan Shukla

Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...

Visit the forum

Question of the Day

SQL Server, Heaps and Fragmentation

A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?

See possible answers