6.5 to 6.5

I want to upgrade our 6.5 sql server to sql server 2000 but first I
want to create another 6.5 first. This way when I screw the pooch I
won't take down our only database.
Anyway I was planning on creating a new database and then restore it
with a dump from the original. If there is an easier way please let
me know.
I've been making daily backups via a CD burner of the folder MSSQL and
backing it up once a week with a dat drive. I"ve also started doing
the dumps each day also.
As you can probably tell I've very new to this.
We use the Platypus 3.0 database frontend by Boardtown.
Thanks for all the help you can give me.<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
Not sure whether dumps from 6.5 can be read but to me, it sounds better to
have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
with 6.5. Run the import database tool, which will copy all objects and data
to SQL 2000.|||Hi,
(You cant restore a SQL 6.5 server database to SQL 2000 server due to
architectural changes.)
The only way to upgrade SQL 6.5 database to SQL 2000 is using the "Upgrade
Wizard" coming with SQL 2000.
You can either perform the upgrade :-
1. In the network using Named pipes protocol
2. Install SQL 6.5 in new server and have the upgrade in the same server
Steps for 1.
1. Install SQL 2000 and SP3a
2. Install SQL 6.5 sp5a
3. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Steps for 2.
1. Install SQL 2000 and SP3a in New server
2. Install SQL 6.5 and SP5a ina new server (With the same folder structure
as existing server)
3. Stop SQL 6.5 server in both servers
4. Copy the physical DAT files (Data and log files) from Existing to new
server in the same folder including system databases
5. STArt SQL 6.5 in server, this will make the new SQL 6.5 server same as
existing
7. In the SQL 2000 server use the upgrade wizard to upgrade. This wizard
will point to a step by upgrade.
Second step will be fast since the upgrade is happening in the same machine.
Incase if you are using the First step then ensure that network is up and
stable.
Thanks
Hari
MCDBA
<kg7poe@.sti.net> wrote in message
news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
> I want to upgrade our 6.5 sql server to sql server 2000 but first I
> want to create another 6.5 first. This way when I screw the pooch I
> won't take down our only database.
> Anyway I was planning on creating a new database and then restore it
> with a dump from the original. If there is an easier way please let
> me know.
>
> I've been making daily backups via a CD burner of the folder MSSQL and
> backing it up once a week with a dat drive. I"ve also started doing
> the dumps each day also.
> As you can probably tell I've very new to this.
> We use the Platypus 3.0 database frontend by Boardtown.
>
> Thanks for all the help you can give me.|||On Sun, 16 May 2004 23:05:51 +0200, "Egbert Nierop \(MVP for IIS\)"
<egbert_nierop@.nospam.invalid> wrote:
><kg7poe@.sti.net> wrote in message
>news:ua3fa0ls3hk30la5trucn6561f47nor9ud@.4ax.com...
>> I want to upgrade our 6.5 sql server to sql server 2000 but first I
>> want to create another 6.5 first. This way when I screw the pooch I
>> won't take down our only database.
>> Anyway I was planning on creating a new database and then restore it
>> with a dump from the original. If there is an easier way please let
>> me know.
>Not sure whether dumps from 6.5 can be read but to me, it sounds better to
>have 2 boxes (or one box with two SQL instances). One with SQl 2000 and one
>with 6.5. Run the import database tool, which will copy all objects and data
>to SQL 2000.
>
Actually I want to resotre another 6.5 with a dump from the original.
Of course I can't even get the new one to work with the backup
database. I made sure its on the same hard drive letter and even
copied over the whole MSSQL folder but so far no luck.