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,365 reads
Luiz Barros
Find and Replace a String in the Whole Database
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,445 reads
Change column type on constrained columns
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,120 reads
Blogs
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases
Comments posted to this topic are about the item How to Use sqlpackage to...
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers