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

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

PowerShell Newbie – Variables

By

This is Week 2 of PowerShell Strikes Back – a four-week May series for...

Read the latest Blogs

Forums

SSRS Is Dead. Here Are Your Real Options

By sgharlow

Comments posted to this topic are about the item SSRS Is Dead. Here Are...

The Distance Metric

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Distance Metric

The New Wave of Security Threats

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Wave of Security...

Visit the forum

Question of the Day

The Distance Metric

In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?

See possible answers