Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Upgrade MS SQL 7 to MS SQL 2005 what the Advisor doesn't tell you?

Avatar of Lowfatspread
LowfatspreadFlag for United Kingdom of Great Britain and Northern Ireland asked on
Microsoft SQL ServerMicrosoft SQL Server 2005
1 Comment1 Solution1015 ViewsLast Modified:
hi,
I'm in the process of upgrading some SQL 7 databases to SQL2005...

I'm happy with the actual process, and have run the upgrade advisor on all code etc...
this identified cases where i'd have to change old style outer join code   *= to left outer etc..

what i'm now concerned about is what the upgrade advisor hasn't warned me about...
e.g. I've just come across some usage of @@IDENTITY, which the advisor didn't give any warnings about... (so i could change to Scope_identity())

apart from @@IDentity , does anyone know of any other areas of code that i should  be worried about?

Lists or websites would be appreciated.

to repeat i've no problems with performing the upgrade itself.. the database will be migrated to sql2005 compatibility..,
i concerned that there maybe other differences that have been ignored / not highlighted in the upgrade advisor...

thanks...