Exactly say, SQL2000 upgrade wisard does not support SQL65. As I mentioned you before, you have to upgrade SQL65 to SQL70 first, the migrate SQL70 to SQL2K.
There is no sure way for database conversion (SQL and Oracle, DB2 even worse).
The simple way and more accurate:
Create same name DB in SQL2000;
Script your Tables in SQL65, modify it to SQL2000 format and run in SQL 2000;
BCP data out to file in business logic order (!) from 65
-- If not sure with BCP, you can use Access, just slow.
BCP files into SQL 2000--- must in PK-FK order.
Script TR, VW, SP from SQL65 (no Fn in 65)
Modify the format to match SQL 2000
Run the Scripts in your new DB in SQL 2000.
This is a pain and risky job, just get more trials before do any thing on PRODUCTION server !!!
Good luck.
--文學城www.wenxuecity.com--
There is no sure way for database conversion (SQL and Oracle, DB2 even worse).
The simple way and more accurate:
Create same name DB in SQL2000;
Script your Tables in SQL65, modify it to SQL2000 format and run in SQL 2000;
BCP data out to file in business logic order (!) from 65
-- If not sure with BCP, you can use Access, just slow.
BCP files into SQL 2000--- must in PK-FK order.
Script TR, VW, SP from SQL65 (no Fn in 65)
Modify the format to match SQL 2000
Run the Scripts in your new DB in SQL 2000.
This is a pain and risky job, just get more trials before do any thing on PRODUCTION server !!!
Good luck.
選擇“Disable on www.wenxuecity.com”
選擇“don't run on pages on this domain”
