Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 sql server 6.5

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-10-08 : 07:56:11
Medha writes "Hello Sir,


I wanted some more information on SQL 6.5.

1. I am trying to create a database, with an existing .DAT file.
2. I have created a Database Device using "DISK REINIT"
3. After creating the device, I am running DISK REFIT. But here I am
getting an error as follows:
"Unable to run DISK REFIT. SQL Server must be booted with the -m option.
Please see your System Administration guide about the Restore Master
procedure."

Can you please help me out in this matter?



Thanks and Regards, "

robvolk
Most Valuable Yak

15732 Posts

Posted - 2003-10-08 : 07:56:45
If you're trying to put a new database on the master.dat device, STOP RIGHT NOW. DO NOT create new databases on this device. Instead, create a new device and put your new database there. User databases should never be placed on the same device(s) as system databases.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-08 : 12:17:33
Why not restore your database in SQL Server 2000 and keep the compatibility mode at 65?

Tara
Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2003-10-08 : 16:15:45
quote:
Originally posted by tduggan

Why not restore your database in SQL Server 2000 and keep the compatibility mode at 65?

Tara



Tara,

I don't think you can restore a 6.5 DB to 2000.

-Chad

http://www.clrsoft.com

Software built for the Common Language Runtime.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-08 : 16:17:41
Yes you can. It allows 60, 65, 70, 80 for the compatibility levels in SQL Server 2000.

Tara
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2003-10-08 : 16:27:45
Think it allows those compatibility levels but only allows restore of v7 and you have to upgrade 6.5.
The compatibility levels are functional not physical.

Never tried it though so could be wrong.


==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

chadmat
The Chadinator

1974 Posts

Posted - 2003-10-08 : 16:28:55
I know you can put your DB in 6.5 compat mode, but you can't restore a 6.5 DB to 2000. You would have to upgrade it.

From BOL:
quote:

Also, it is not possible to restore a database backup created using SQL Server version 6.5 or earlier. Database backups created using SQL Server 6.5 or earlier are in a format incompatible with SQL Server 2000.



-Chad

http://www.clrsoft.com

Software built for the Common Language Runtime.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-08 : 16:30:07
Ah, very true. It's been a while since I've done an upgrade from 6.5 to 2000. But my question remains except it should read:

Why not upgrade your database to SQL Server 2000 but keep the compatibility level at 65?

Tara
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2003-10-08 : 17:22:48
I think what the questioner is trying to do is the equivalent of an attach database which for 6.5 was done by a disk reinit and refit. Can't remember much about them but after a bit of research disk reint add the device to sysdevices, disk refit recreates sysdatabases and sysusages (in master) from sysdevices. You will need to be careful about the device number and size.

Might be better to just create a new database of exactly the same size, stop the server, copy your dat files to the newly created ones then start the server again.

Not surprising it will need to be in single user mode to do a refit as it will overwrite info for all databases.


==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2003-10-08 : 19:06:44
quote:
Why not upgrade your database to SQL Server 2000 but keep the compatibility level at 65?
Perhaps he/she doesn't have the MONEY for a new SQL Server license, or for new hardware to run it on. You have to stop suggesting that an upgrade will solve every problem.
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2003-10-08 : 19:18:44
And I thought v6.5 was a great product
It forced developers to know what they were doing to get something running efficiently even on small amounts of data and you had a good chance of guessing what any query plan would be like and DBAs had to have some experience to get anywhere.

Cursors were a problem in all cases, views were slow, no dts/linked servers to confuse matters.
You didn't have to keep qualifying every statement about what would be ok and what wouldn't.

Basically things didn't work straight away rather than failing after a couple of years.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-08 : 19:21:38
I mentioned it because it appears that s/he is trying to do an attach. It's much simpler in SQL Server 2000.

BTW, I loved 6.5 as well. I worked on it up until about a year ago.

Tara
Go to Top of Page
   

- Advertisement -