Re: Upgrading from SQL 6.5 to SQL 2000

From: Leo (none_at_none.com)
Date: 08/20/04 

Date: Fri, 20 Aug 2004 08:53:14 -0400

Thanks for the replies. I should have mentioned that I am upgrading the 6.5
database to a physically separate SQL server 2000. So I need to actually
tansfer the database. If I detach it then copy it to the new server then
upgrade it will that work? If so that is pretty straight forward then

Thanks again

"Hari Prasad" <hari_prasad_k@hotmail.com> wrote in message
news:uXV5EonhEHA.1276@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> You have to upgrade the database to SQL 2000 using the upgrade wizard
first.
> After the completion of successfull upgrade only you will be able to
switch
> between SQL 2000 and SQL 6.5.
>
> What is the fastest way to do this? Can I use SQL server switch?
>
> Only way to migrate is to use the SQL server Upgrade wizard.
>
> If so will it impact the original 6.5 database?
>
> No impact.. Upgrade will not make any changes to SQL 6.5 databases.After
> upgrade u could use switch option to see the SQL 6.5 databases
>
> Does it have to be done when there's not transactions pending for the
> database or can it be done at any time?
>
> Yes. During upgrade users can not Access SQL server 6.5, because the
upgrade
> process will stop and start services inbetween.
>
>
> You could see the detailed step by step to upgrade from SQL 6.5 to SQl
2000
> in Books online.
>
> Search for "Version 6.5 to SQl server 2000"
>
> Thanks
> Hari
> MCDBA
>
>
> "David G." <david_nospam@nospam.com> wrote in message
> news:OQsp#XjhEHA.3016@tk2msftngp13.phx.gbl...
> > Leo wrote:
> > > I have a fairly large database in SQL 6.5 at this point. I'd like to
> > > upgrade it to SQL 2000. What is the fastest way to do this? Can I use
> > > SQL server switch? If so will it impact the original 6.5 database?
> > > Does it have to be done when there's not transactions pending for the
> > > database or can it be done at any time? I want to upgrade it as a
> > > test first, then if that goes ok, I'd like to do it again as a final
> > > upgrade and put it in production
> > >
> > > Thanks for your help
> >
> > Why not install SQL Server 2000 on another PC for testing. The switch,
> > as I recall, lets users switch between SQL Server 2000 and older SQL
> > Server versions. I do not think there is any overlap of data (i.e. no
> > shared files). I only think that SQL Server was designed to only allow
> > one version to run at a time. What I'm saying (if I;m correct) is that
> > while SQL Server 2000 is running SQL 6.5 will not be, and vice-versa. I
> > welcome corrections on this.
> >
> > --
> > David G.
> >
>
>

Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... looking at the database table information, ... Microsoft Windows SharePoint Services 2.0 ... Can we asume you mean SQL Server 2005? ... The upgrade identified that there was a previous ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrade from MSDE to SQL
    ... Hard to say whether the database is of any use to you now you are partway ... upgrade just in case. ... But FIRST I would in any case see if adding SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot view DB properties
    ... # Ran the setup and upgraded the existing SQL Server 8.00.818 to SQL Server ... owner was NULL after the UPgraded finished successfully. ... The proposed new database owner is already a user or aliased in the ... Sorry, I don't understand, what do you mean by "In-Place Upgrade"? ...
    (microsoft.public.sqlserver.security)
  • Re: Upgrade 2000 to 2005
    ... That way, if there is a failure in the upgrade process, you at ... Senior Database Administrator ... Real-world stuff I run across with SQL Server: ... side and move the databases but the hardware just aint there. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Upgrading from SQL 6.5 to SQL 2000
    ... transferring the objects and data from within Enterprise Manager. ... > database to a physically separate SQL server 2000. ... >> You have to upgrade the database to SQL 2000 using the upgrade wizard ...
    (microsoft.public.sqlserver.tools)