Articles

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.

2010-06-23

3,366 reads

External Article

Creating XML in SQL Server

XML has become a common form of representing and exchanging data in today's information age. SQL Server introduced XML-centric capabilities in SQL Server 2000. That functionality has been expanded in later releases. One aspect of working with XML is creating XML from relational data, which is accomplished utilizing the FOR XML clause in SQL Server.

2010-06-22

4,464 reads

Blogs

2025 Wrapped for Steve

By

I’ve often done some analysis of my year in different ways. Last year I...

The Book of Redgate: Spread across the world

By

This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...

Merry Christmas

By

Today is Christmas and while I do not expect anybody to actual be reading...

Read the latest Blogs

Forums

Database security permissions save script

By Srinivas Merugu

Comments posted to this topic are about the item Database security permissions save script

Database backup job steps

By Pete Bishop

I have a SQL Agent job for backing up a set of Analysis Services...

SQL Server 2025 Backup Compression Algorithm

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Backup Compression...

Visit the forum

Question of the Day

The Large Encoded Value

I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?

See possible answers