External Article

Making your SQL Server database changes backward compatible: Adding a new column

As multi-tier architectures grow over time, it is often challenging to coordinate those changes across the data, logic and presentation tiers. Unless planned and implemented carefully, an act as simple as adding a column to a table can grind all of the components of your application to a halt. While some of us have comfortable 12-hour maintenance windows every weekend, many of us are bound by service level agreements that are much more strict. So we must find ways to introduce fixes and new features with zero downtime, and without requiring every single component to be refactored at the same time.

Blogs

Automatic Index Compaction

By

Index maintenance has always meant nightly jobs and a window you have to defend....

Monday Monitor Tips: Virtual Machine Usage and Cost

By

One of the things I’ve been requesting for a number of years is cost...

Advice I Like: Respect

By

“Don’t aim to have others like you; aim to have them respect you.” –...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

SQL Server Still Wins

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Still Wins

DBCC CHECKDB Limits I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits I

Visit the forum

Question of the Day

DBCC CHECKDB Limits I

When running DBCC CHECKDB on SQL Server 2025, can I specify only the Resource Database?

See possible answers