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

The fundamental requirements of a reporting system

By

There are some fundamental boxes that your reporting system must tick. ✅ The figures...

Seeing the Bigger Picture: How A Monitoring Tool Changed My Approach to Estate Management

By

When it comes to managing complex database environments, having the right monitoring solution is...

A New Word: Foilsick

By

foilsick – adj. feeling ashamed after revealing a little too much of yourself to...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

count the number of NULLs in a row

By water490

Hi everyone I have a SP that finds the average based on 3 tables. ...

Deleting data in large table

By Jackie Lowery

I have a large table with 17M+ rows for our package record audits.  I've...

Visit the forum

Question of the Day

SQL Server Ghosts

For Halloween, what are ghost records?

See possible answers