Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2007-03-26
1
Medium Priority
?
975 Views
Last Modified: 2012-06-21
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...    
0
Comment
Question by:Lowfatspread
1 Comment
 
LVL 143

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 2000 total points
ID: 18791748
>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

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple.  The final solution for this task involved creating a custom text parser and then reading…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question