Editorial

SQLServerCentral Editorial

Containers Are The Present, Not the Future

  • Editorial

Last week was the MVP Summit. This year included a bunch of very technical discussions about some of the future of the Microsoft Data Platform (a big thank you goes to Slava Oks, Bob Ward, and all the team for a great job). I can’t share much since it was all under NDA. All I […]

5 (1)

You rated this post out of 5. Change rating

2019-03-30

502 reads

SQLServerCentral Editorial

Query Tuning Assistant: A Tool for Upgrades

  • Editorial

If you have been working with SQL Server long enough, you have probably been involved with a SQL Server 2000 to 2005 upgrade. It was painful for many shops due to the deprecation of some features like DTS and the removal of old-fashioned comma joins with the plus operator. It was worth the pain as […]

You rated this post out of 5. Change rating

2019-03-25

1,203 reads

Blogs

Understanding Zonal Redundancy in Azure SQL MI

By

Do you know what happens when you enable zonal redundancy for your SQL managed...

SQL Server Database Compatibility Levels

By

Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting   If you’ve...

The PASS Summit on Tour in the Netherlands

By

The PASS Summit goes on tour this year, with the final date the first...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Best Health Insurance Plans for Truck Drivers

By thetruckersnetwork

Find affordable and reliable medical insurance tailored specifically for truckers with Trucker’s HealthCare. Designed...

Upgraded VS2019 to version 16.11.49 but I cannot access my original SSIS package

By water490

Hi I upgraded to new version of VS2019 to 16.11.49.  My original SSIS package...

Visit the forum

Question of the Day

The Updated Columns List

I have this table in SQL Server 2022:

CREATE TABLE CustomerLarge
  (CustomerID               INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED
 , CustomerName             VARCHAR(20)
 , CustomerContactFirstName VARCHAR(40)
 , CustomerContactLastName  VARCHAR(40)
 , Address                  VARCHAR(20)
 , Address2                 VARCHAR(20)
 , City                     VARCHAR(20)
 , CountryCode              CHAR(3)
 , Postal                   VARCHAR(20)
)
GO
If I check the columns_updated() function return in a trigger, what is the data returned?

See possible answers