Database Design

External Article

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

  • Article

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.

2010-06-23

3,366 reads

Blogs

Rolling Back a Broken Release

By

We had an interesting discussion about deployments in databases and how you go forward...

A bespoke reporting solution doesn’t have to cost the earth

By

You could be tolerating limited reporting because there isn’t an off the shelf solution...

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Read the latest Blogs

Forums

Lots of FKs

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Lots of FKs

Real-time On-prem SQL Server Data in Excel – Over the Internet

By Cláudio Tereso

Comments posted to this topic are about the item Real-time On-prem SQL Server Data...

Can You Let Go of Determinism

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Can You Let Go of...

Visit the forum

Question of the Day

Lots of FKs

In SQL Server 2025, what are the most outgoing and incoming FK references a table can have?

See possible answers