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
go_radicalAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
are you speaking of this question:
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_22893924.html

now, what is your exact problem?
0
Ted BouskillSenior 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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
go_radicalAuthor Commented:
OK! I changed all the prefixes in the code to dbo. Now everything works fine.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.