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

Understanding Fabric Ontology

By

What problem is Fabric Ontology trying to solve? For years, most data conversations have...

QUOTENAME Basics: #SQLNewBlogger

By

Recently I ran across some code that used a lot of QUOTENAME() calls. A...

When growing companies outgrow Excel

By

There are some telltale signs that your growing business has outgrown Excel for your...

Read the latest Blogs

Forums

Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployment...

QUOTENAME Quote Parameters

By Steve Jones - SSC Editor

Comments posted to this topic are about the item QUOTENAME Quote Parameters

Limit the Blast Radius

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limit the Blast Radius

Visit the forum

Question of the Day

QUOTENAME Quote Parameters

When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?

See possible answers