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

On Speaking Well

By

Professor Patrick Winston of MIT used to give a one-hour talk about how to...

Monday Monitor Tips: Oracle Custom Metrics

By

One of the popular features of Redgate Monitor has been the ability to add...

Walking Through a Planned Failover: SQL Server Always On Availability Groups on Kubernetes

By

When building the sql-on-k8s-operator, I wanted to make sure it could handle both planned...

Read the latest Blogs

Forums

Are Akashic Records Course Fees Worth It? IIVS Review & Opinions

By iivs45

I’ve been exploring different platforms to learn about spirituality in a more structured way,...

Troubleshooting WQL in custom PBM conditions?

By mastershake

Hi, I'm currently trying to implement policy based mgmt with a condition to query...

Analysis of Locking Issues on Secondary Replicas in AlwaysOn Availability Groups

By abdalah.mehdoini

We have an AlwaysOn architecture with four replicas: two running in synchronous commit mode...

Visit the forum

Question of the Day

The Vector Data Type

What is the vector data type in SQL Server?

See possible answers