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,375 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,375 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,460 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,126 reads
By James Serra
Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....
By Steve Jones
I recently started playing with the MCP Server for SQL Server, which is a...
If you spend your days tuning queries, managing pipelines, or keeping a production database...
I've got multiple databases on 2 SQL 2019 CU32 servers , all using the...
Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...
Putting this here as we're currently on SQL Server 2019 installed on Windows Server...
I have added a few indexes to one of my tables in SQL Server 2025:
ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
PRIMARY KEY (CustomerID);
-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disableI see this when I check the index status:
I decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuildAfter I do this, what will I see for the index status? See possible answers