November 2, 2007 at 6:07 am
Hi ,
The current database uses
1) Hints
2) subqueries in place of joins
3) global variables like @@rowcount in order to check how many rows should be returned to the user
4) there are no foreign key relationships for performance reasons
This is all in accordance to SQL Server 2000
I am assuming that the same set of stored procedures will be executed on SQL Server 2005 ...
Should i expect a variation in the behavior of the stored procedures?
What should the course of action ... should i start modifying the stored procedures now on or should i wait for any problem to occur and then start modifying the stored procedure
As a developer I am trying to foresee the problems ...
Please do let me know your experiences and views .. which will help me gear up
Thanks
November 2, 2007 at 6:27 am
I also wish to add that .... Currently error processing is done by checking @@error ..Would it be wise to change it to Try Catch
November 2, 2007 at 9:00 am
I suggest you download and run SQL Server Upgrade Advisor http://www.microsoft.com/downloads/details.aspx?FamilyID=1470e86b-7e05-4322-a677-95ab44f12d75&DisplayLang=en. It will list for you all the things in existing stored procedures that either won't work or work differently in SQL 2005.
Greg
Greg
November 2, 2007 at 10:35 am
Most things should function the same. You might need to rebuild indexes/update statistics, but you can set the upgraded db to SQL 2000 mode (8.0 compatability) and things should work.
If possible, you should dry run this to a test database after running the Upgrade Advisor.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply