Restoring SQL 6.5 to SQL 2000

Yes, after all these years, we're going to restore some of our SQL 6.5
databases to SQL 2000. Microsoft made a pretty invasive way to do this
with the SQL Upgrade Wizard, which you shouldn't run during production
hours because it will stop the SQL services and copy over ALL objects
without asking you which ones you want to copy over. I abandoned that
wizard in a hurry. Thank you, Microsoft. Classic! I always like a good
Microsoft laugh while I rdesktop from my Ubuntu Linux workstation. Old
Bill likes to keep these jokes coming. He should join a comedy club or
something.

I was practicing with Pubs, which I recommend you try first.

I found that if I use the SQL DTS Wizard in SQL 2K, I can migrate over
all tables fairly nicely and smoothly and without having to have an
outage window on 2 production servers. Where it breaks down is with any
non-table object. Luckily, the only other items are indices and stored
procedures, and for those I can just script out to a text file, then
run them in a query analyzer to get these changes applied on the SQL 2K
server.

Hope this helps anyone trying to do this venture.

Sounds like you're well on your way.  This document may help you or someone
else reading this thread in the future.

How to Upgrade SQL Server 6.5 and 7.0 to SQL Server 2000
http://www.microsoft.com/technet/pr...oy/sqlugrd.mspx

HTH

Jerry

<googlemike@hotpop.com> wrote in message
news:1127932384.714757.217360@g47g2000cwa.googlegroups.com...
> Yes, after all these years, we're going to restore some of our SQL 6.5
> databases to SQL 2000. Microsoft made a pretty invasive way to do this
> with the SQL Upgrade Wizard, which you shouldn't run during production
> hours because it will stop the SQL services and copy over ALL objects
> without asking you which ones you want to copy over. I abandoned that
> wizard in a hurry. Thank you, Microsoft. Classic! I always like a good
> Microsoft laugh while I rdesktop from my Ubuntu Linux workstation. Old
> Bill likes to keep these jokes coming. He should join a comedy club or
> something.
>
> I was practicing with Pubs, which I recommend you try first.
>
> I found that if I use the SQL DTS Wizard in SQL 2K, I can migrate over
> all tables fairly nicely and smoothly and without having to have an
> outage window on 2 production servers. Where it breaks down is with any
> non-table object. Luckily, the only other items are indices and stored
> procedures, and for those I can just script out to a text file, then
> run them in a query analyzer to get these changes applied on the SQL 2K
> server.
>
> Hope this helps anyone trying to do this venture.
>

Hi,

I agree with you partially as far as downtime is concerned. But I strictly
recommend you to use the
upgrade wizard to upgrade the SQL 6.5 databases to SQL 2000. This will
reduce lots of pain
and will reduce lots of manual work.

I feel that moving the databases manually using DTS will take much higher
time then upgrade wizard, as well as you might
loose some data which is being transacted during your DTS.

So I strogly suggest you to get some downtime from business and do the
Upgrade wizard to do the upgrade. Ensure that you do a
Update statistics and DBCC before upgrade.

Thanks
Hari
SQL Server MVP


<googlemike@hotpop.com> wrote in message
news:1127932384.714757.217360@g47g2000cwa.googlegroups.com...
> Yes, after all these years, we're going to restore some of our SQL 6.5
> databases to SQL 2000. Microsoft made a pretty invasive way to do this
> with the SQL Upgrade Wizard, which you shouldn't run during production
> hours because it will stop the SQL services and copy over ALL objects
> without asking you which ones you want to copy over. I abandoned that
> wizard in a hurry. Thank you, Microsoft. Classic! I always like a good
> Microsoft laugh while I rdesktop from my Ubuntu Linux workstation. Old
> Bill likes to keep these jokes coming. He should join a comedy club or
> something.
>
> I was practicing with Pubs, which I recommend you try first.
>
> I found that if I use the SQL DTS Wizard in SQL 2K, I can migrate over
> all tables fairly nicely and smoothly and without having to have an
> outage window on 2 production servers. Where it breaks down is with any
> non-table object. Luckily, the only other items are indices and stored
> procedures, and for those I can just script out to a text file, then
> run them in a query analyzer to get these changes applied on the SQL 2K
> server.
>
> Hope this helps anyone trying to do this venture.
>