August 31, 2005 at 12:32 pm
Hi All,
First things first. This is my first entry on these forums. Hello to everybody here..
I am a coldfusion web developer and have been working on SQL Server now for the past 2- 3 yrs. We are getting a new SQL 2000 machine and would like to move a 6.5 database to 2000.
Is this is a simple backup(on 6.5) and a restore on 2000 machine or should the move be done in a totally different way.
I am assuming that there would be compatibility settings similar to what we have in SQL 7.0
Let me know if I you need more info
tx in advance
mota
August 31, 2005 at 1:08 pm
SQL Server 6.5 to SQL Server 2000 can be complicated because I can write 200 pages and I have not finished with the difference in both systems. I would use the upgrade wizard and go in to see the results because you are going from Linked list files to ODS(on disk system), 225 kb page to 8000kb, page level locking to rowlevel locking and DRI( declearative referential integrity) in SQL Server 2000. Then backup and restore the new database to see the results. This should get you started. Hope this helps
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
August 31, 2005 at 1:46 pm
You can do it. Database options for SQL 2K are for SQL 6.0 to present. Of course like Gift stated there may be gotchas.
If possible you could script the items out and manually run the scripts, use the upsize wizard, import/export wizard, etc....
IMHO no matter which way is used you may run into issues. BEST ADVICE, TEST, TEST, TEST
Oh and TEST
Good Hunting!
AJ Ahrens
webmaster@kritter.net
August 31, 2005 at 2:08 pm
tx guys.
Looks like its not gonna be a simple upgrade kinda thingi.
Tx for the warning
mota
September 1, 2005 at 12:08 am
You need to run the upgrade wizard on the 6.5 databases, or export the data in some other manner (e.g. BCP or DTS).
SQL Server 6.x database dumps (backups) cannot be restored onto a SQL Server 2000 server.
September 2, 2005 at 9:23 am
Things can be simple. Don't let the 'potential gotchas' interfere with the goal. Try the 'Upgrade Wizard' on a test database. It does produce an audit of what issues it encounters. However I would be careful if it is a very large database 10-20+ Gb. Execution on larger databases can take quite a while. Also I suggest that both SQL Servers be on the same network subnet and have 100 Mb Full Duplex connectivity since the 'wizard' will have to transfer all of the base data from one database to another.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply