December 3, 2002 at 11:45 am
Just when you thought it was safe. I have just been informed that we have a SQL Server 4.2 version running out in one of our branches and they would like to preserve the database in 7 or 2K.
I haven't seen any of this yet. They're working on the communications as I type. Is they're an upgrade to 7.0 from 4.2?
Would I be better off BCP out- does that exists for 4.2?
Has anyone out there upgrade 4.2 to 7.0 +
Don't shoot me for not knowing about the database - I'm still playing catch up here.
John Zacharkan
John Zacharkan
December 3, 2002 at 3:21 pm
You have to follow the full upgrade path thru each major version, I never went that far back but did do an upgrade in a test lab from 6.0 to 6.5 to 7.0. And there are no guarantees that it will upgrade smoothly and without some fixing along the way.
BCP it out would be far better and less time consuming. If there is an app attached to the frontend you may need to modify it. You may be able to save a little time if you can use ODBC and attached with Access to pull the data or even SQL 7 but you are in for a lot of fun I would think.
December 3, 2002 at 3:54 pm
Upgraded from 4.2 to 6.5. I think bcp might be the easiest. Or get a couple servers and stage the upgrade from 4.2 to 6.x, then to 2000. Check the data, get row counts for each table at each stage and ensure it is still working.
Steve Jones
December 3, 2002 at 4:35 pm
Having done this myself several times now, I would strongly suggest a bcp out of the data, scripting of the database, and building of a new database.
Should I have said very strongly?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply