Importing or attaching a database

I had to reinstall sql7 and I now need to access my old
database. It is in the mssql7 data directory, but it does
not show up under enterprise manager. Is there a way
to "import" it?
Thanks for any help
Try using sp_attach_db. See SQL Server Books Online for more information on
this procedure, and examples.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"GB" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa3f01c465ec$74153290$a301280a@.phx.gbl...
> I had to reinstall sql7 and I now need to access my old
> database. It is in the mssql7 data directory, but it does
> not show up under enterprise manager. Is there a way
> to "import" it?
> Thanks for any help

Importing or attaching a database

I had to reinstall sql7 and I now need to access my old
database. It is in the mssql7 data directory, but it does
not show up under enterprise manager. Is there a way
to "import" it?
Thanks for any helpTry using sp_attach_db. See SQL Server Books Online for more information on
this procedure, and examples.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"GB" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa3f01c465ec$74153290$a301280a@.phx.gbl...
> I had to reinstall sql7 and I now need to access my old
> database. It is in the mssql7 data directory, but it does
> not show up under enterprise manager. Is there a way
> to "import" it?
> Thanks for any help

Importing or attaching a database

I had to reinstall sql7 and I now need to access my old
database. It is in the mssql7 data directory, but it does
not show up under enterprise manager. Is there a way
to "import" it?
Thanks for any helpTry using sp_attach_db. See SQL Server Books Online for more information on
this procedure, and examples.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"GB" <anonymous@.discussions.microsoft.com> wrote in message
news:2aa3f01c465ec$74153290$a301280a@.phx
.gbl...
> I had to reinstall sql7 and I now need to access my old
> database. It is in the mssql7 data directory, but it does
> not show up under enterprise manager. Is there a way
> to "import" it?
> Thanks for any help

Importing from SQL7 using DTS wizard

We are trying to import data from a sql 7 machine into sql 2000 using
import wizard in DTS. One of the tables has in excess of 80 million
rows.

The first time we did this it worked fine no problems. However we had
to recreate the database, and it has not worked since.

The error message is reported as ' the log file for 'dbname' is full'.
This happens regardless of the fact that there is 100GB free on disk,
and that the database data and log files are both set to autogrow. The
recovery model is set to simple.

When imported the data.mdf file should be around 20GB.

Would anyone know what is causing this or how to get around this
without going down the SQL7 install, restore and upgrade to sql2000
route?

Any help would be appreciated greatly.Hi

You may want to try attaching the mdf and ldf files from the SQL 7 box onto
the SQL 2000 box and then making any modifications required or restore a
backup.

You don't say how big the log file is. If it is set to grow by a percentage
that value may be larger than the available disk space.

Check out

http://support.microsoft.com/defaul...b;en-us;Q314546
http://support.microsoft.com/defaul...ben-us%3b224071
http://msdn.microsoft.com/library/d...ar_da2_1uzr.asp

John

"John Gill" <pizzaboyo@.yahoo.co.uk> wrote in message
news:a8be1015.0311070405.17c37eb@.posting.google.co m...
> We are trying to import data from a sql 7 machine into sql 2000 using
> import wizard in DTS. One of the tables has in excess of 80 million
> rows.
> The first time we did this it worked fine no problems. However we had
> to recreate the database, and it has not worked since.
> The error message is reported as ' the log file for 'dbname' is full'.
> This happens regardless of the fact that there is 100GB free on disk,
> and that the database data and log files are both set to autogrow. The
> recovery model is set to simple.
> When imported the data.mdf file should be around 20GB.
> Would anyone know what is causing this or how to get around this
> without going down the SQL7 install, restore and upgrade to sql2000
> route?
> Any help would be appreciated greatly.