February 2, 2011 at 8:39 am
Hi , I´d like to know the right procedure to migrate an old version sql 6.5 to Sql 2000 and the right Sql 2000 Collation or equivalent that I need to install in the new Sql 2000 before migrate.
This is the 6.5 collation .
Sort Order Description ------------------------------------------------------------------
Character Set = 1, iso_1 ISO 8859-1 (Latin-1) - Western European 8-bit character set. Sort Order = 52, nocase Case-insensitive dictionary sort order for use with several We stern-European languages including English, French, and German . Uses the ISO 8859-1 character set. Characters, in Order ------------------------------------------------------------------
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ® ¯ ° ± ² ³ ´ µ ¶ ·
I was wondering if I could use the DTS to transfer data when the sql2000 is already on.
I think that I need to migrate to 2000 before migrate to 2005 or higher , I'm right ??
Thks a lot.
Alex.
February 2, 2011 at 8:49 am
If you upgrade to SQL 7, you can move to 2005.
http://msdn.microsoft.com/en-US/library/ms143393%28v=SQL.90%29.aspx
However, DTS was better in SQL 2000. You ought to be able to restore the database from v6.5 backup to 2000 directly, and that would set your collation. In newer versions of SQL, you don't need the server collation to match, so you can have separate collations for the database.
February 3, 2011 at 11:55 am
Hi...thks for your quick response
I tried to restore the database directly in sql 2005 but I got this error.
Msg 3241, Level 16, State 0, Line 1
The media family on device 'D:\Database.dat' is incorrectly formed. SQL Server cannot process this media family.
Msg 3013, Level 16, State 1, Line 1
RESTORE FILELIST is terminating abnormally.
The 6.5 Backup it's fine, because I restored the same backup on the 6.5 server and there is no problem.
February 3, 2011 at 12:23 pm
I don't remember being able to do restores from 6.5 to 7 or 2000. The file structure is ENTIRELY different, first big difference V4-6.5 used 2K pages, 7-Present use 8K pages.. And thats only the start.. I think you need to use the wizard and migrate the database from 6.5 to 2000 and then you should be able to attach or backup/restore it to any same or higher version..
CEWII
February 3, 2011 at 1:46 pm
I thought that SQL 7/2000 could restore up from v6.5, but maybe not. This mentions the upgrade wizard, which might just be a DTS transfer
http://msdn.microsoft.com/en-us/library/aa176562(v=SQL.80).aspx
February 3, 2011 at 1:52 pm
I used the upgrade wizard to go from 6.5 to 2000 in ~2002, it worked pretty good. That wizard didn't do anything with DTS since it didn't exist in 6.5. It might have handled it for 7 to 2000...
CEWII
February 3, 2011 at 1:59 pm
Isn't the upgrade wizard part of 2000 though, not v6.5? So it might be doing a script objects/ bcp data, which is all that the DTS xfer database does.
In any case, I think that to move you might need to do that to get to 2000, then upgrade those dbs to 2005.
February 3, 2011 at 3:04 pm
Ok...I'll try to do it using the upgrade wizard, and I'll let you know if works or not..
Thks a lot for your comments, I hope...everyting goes well
February 4, 2011 at 12:44 pm
Sorry I am a little late to the party but Elliott is correct. Using the Wizard is the most efficient and less stressful way to upgrade a 6.5 database. The one annoying part of upgrading to 7 was having to step through the service packs.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
February 4, 2011 at 2:34 pm
I don't think you have to go through 7, I seem to remember going directly from 6.5 to 2000, this was in like 2002 so it was a while ago but I'm pretty sure we didn't go through 7..
CEWII
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply