July 25, 2003 at 2:27 am
Hello,
We are a systems integrator and need to upgrade our product's back-end database from SQL Server 7.0 to 2000. I'm curious if there is an exhaustive list anywhere of T-SQL commands, etc. that work differently on 2000 as opposed to 7.0. In other words, our application uses approx. 100 stored procedures, 25 tables, and 20 views -- is there a way to avoid having to go through each of these one-by-one to make sure that they return the same data, update/insert/delete data in the same way, etc.?
Also, when one loads 2000 on a box that already has 7.0 on it, are there any issues to watch out for in terms of the database being migrated from 7.0 to 2000 properly?
Thanks,
Alan G.
July 25, 2003 at 6:02 am
Its been a while since I upgraded, but I dont remember any commands that work differently. It's a pretty painless upgrade. Only thing you need to do is run sp_updatestats on each db after the upgrade, the index stats are different in SQL2K.
Long term, it might be worth your while to write those tests anyway, that way if you upgrade again or port to a different platform, you've got a test ready to run.
Andy
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply