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

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...    
LVL 50
LowfatspreadAsked:
Who is Participating?
 
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
>I've just come across some usage of @@IDENTITY
well, sql server 2005 still supports @@identity, but it is indeed more secure to use scope_identity().
however, if your code worked, it will continue to work fine with @@identity, hence the advisor does not (need) to tell you.

I am not aware of anything that the advisor would not tell (that would make things break)...

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.