DBAs should learn to go through the proper channels to make updates. This means using system stored procedures and statements to make configuration changes, instead of manually hacking the system tables. Using the right tools is important because it allows Microsoft to modify the internal structures of the system objects without breaking your code.
My advice to anyone directly manipulating the system tables is to re-write the code now so that migration to SQL Server 2005 will not break your applications.
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on Microsoft SQL Server 2005
Related Q&A from Adam Machanic
Migrating to SQL Server 2005 from SQL Server 2000 is a hefty feat when compared to upgrading from 7.0 to SQL Server 2000. Site expert Adam Machanic ... Continue Reading
Multiple readers can sometimes read the same row simultaneously causing a false result. SQL Server 2005 expert Adam Machanic suggests modifying the ... Continue Reading
SQL Server 2005 and T-SQL do have differences. The advantages and disadvantages would depend user environment as described by SQL Server 2005 expert... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.