Testing all procs before upgrading to Compatibility Level 90
You can use this script to check if any procs will break under compatibility level 90.
2012-03-08 (first published: 2008-01-29)
4,323 reads
You can use this script to check if any procs will break under compatibility level 90.
2012-03-08 (first published: 2008-01-29)
4,323 reads
Find and Replace a string in all string fields (char, varchar, etc) of all tables in the database.
2011-10-27 (first published: 2008-02-08)
3,438 reads
Use this proc if you need to alter a column that is part of a primery key
2008-02-04 (first published: 2007-12-10)
1,114 reads
By Arun Sirpal
Do you know what happens when you enable zonal redundancy for your SQL managed...
By Kevin3NF
Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting If you’ve...
By Steve Jones
The PASS Summit goes on tour this year, with the final date the first...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi I upgraded to new version of VS2019 to 16.11.49. My original SSIS package...
I've written this code, but it is showing right now as 2 rows per...
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) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers