dbo Prefix after migrate from MS SQL 2000 to 2005

There is already a question with the same problem "Restoring SQL Server 2000 db to SQL Server 2005 db user issues" posted with a solution "I got it.  It seems there is an order to things.  I can now run the sp's either way.  I don't have time to write it up but I will in case someone else runs into this issue."

But I can't find the solution in detail. How is it possible to get the solution.

Many thanks
Who is Participating?
Ted BouskillConnect With a Mentor Senior Software DeveloperCommented:
The schema for many system tables changed in SQL 2005.  However, it's backward compatible and if you restore a SQL 2000 DB on SQL 2005 it will honor the old system table names.

Using the 'dbo' prefix is recommended because it improves performance.  In some cases it can be substantial.  For example, SQL won't cache execution plans for store procedures that don't use the dbo prefix within.

Many people mistakenly think that adding the prefix simply prevents an owner lookup (which is correct) however, it's far more than that.

I manage a team of developers and if they don't use the prefix they don't pass code review.
Guy Hengel [angelIII / a3]Billing EngineerCommented:
are you speaking of this question:

now, what is your exact problem?
go_radicalAuthor Commented:
OK! I changed all the prefixes in the code to dbo. Now everything works fine.
All Courses

From novice to tech pro — start learning today.