October 29, 2008 at 8:19 am
I am migrating from sql server 2000 to sql server 2008.
Updating system table sysobjects is presented in legacy code.
How can I solve this problem?
October 29, 2008 at 9:40 am
You change the code so that it doesn't try to update the system tables. Then you run a checkDB to see how much mess there already is in the DB's metadata. If it's not possible to change the code then you will have to keep that app on SQL 2000.
The system tables cannot be updated on SQL 2005 or 2008. It was strongly recommended against even on SQL 2000 with really large warnings in Books Online.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 29, 2008 at 10:09 am
What does the code do? Perhaps we have another solution.
October 30, 2008 at 3:18 am
Thanks for answers! Updating system tables really is not good approach.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply