Having problems importing MDF file (no LDF)

We have a server where the LDF file was deleted by someone. The
software vendor (Platypus) actually recommended doing this. I'm now
stuck with trying to get this DB back up and running.
I tried the methods listed here, but they were not successful. The
failure occurs at the point of rebuilding the LDF file. It ran for
over 15 hours with no effect.
Any ideas here?
Thanks,
DougYou didn't actually mention the "methods listed here", but try
sp_attach_single_file_db.
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||Only sp_attach_db creates the t-log file if it's not existed too.
--
Ekrem Önsoy
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||On Oct 7, 4:46 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> You didn't actually mention the "methods listed here", but try
> sp_attach_single_file_db.
> <nerd1...@.gmail.com> wrote in message
>
I tried that as well as the method listed at
http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic4869.aspx|||Your software vendor is insane. Is the database in suspect mode or is it
failing to attach period, when using the sp_attach_single_db proc?
<nerd1701@.gmail.com> wrote in message
news:1191784420.394668.322780@.o80g2000hse.googlegroups.com...
> We have a server where the LDF file was deleted by someone. The
> software vendor (Platypus) actually recommended doing this. I'm now
> stuck with trying to get this DB back up and running.
> I tried the methods listed here, but they were not successful. The
> failure occurs at the point of rebuilding the LDF file. It ran for
> over 15 hours with no effect.
> Any ideas here?
> Thanks,
> Doug
>|||On Oct 7, 7:11 pm, "Mike C#" <x...@.xyz.com> wrote:
> Your software vendor is insane. Is the database in suspect mode or is it
> failing to attach period, when using the sp_attach_single_db proc?
>
It fails when trying to do sp_attach_single_db with the error that the
log file is missing or invalid.
Doug|||Basically, you will want to restore from your backup. Even if you find some hack to get this
database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
new log file to be created but the reason it complains as it is is because SQL Server need the log
file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
might find will leave you with "half performed transactions" i.e., logically inconsistent data (like
an order for a customer that doesn't exist). SQL Server also uses transactions to protect
modifications against meta-data so you risk having a physical corruption as well.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191858236.871322.193030@.g4g2000hsf.googlegroups.com...
> On Oct 7, 7:11 pm, "Mike C#" <x...@.xyz.com> wrote:
>> Your software vendor is insane. Is the database in suspect mode or is it
>> failing to attach period, when using the sp_attach_single_db proc?
> It fails when trying to do sp_attach_single_db with the error that the
> log file is missing or invalid.
> Doug
>|||On Oct 8, 12:44 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Basically, you will want to restore from your backup. Even if you find some hack to get this
> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
> new log file to be created but the reason it complains as it is is because SQL Server need the log
> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
> might find will leave you with "half performed transactions" i.e., logically inconsistent data (like
> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
> modifications against meta-data so you risk having a physical corruption as well.
>
We tried to restore the backups, but it's asking for a file that
doesn't exist.
For example, we tell it to restore from Wednesday, but it asks for
Friday also. Which doesn't exist.
This isn't my machine directly but belongs to someone else that I'm
trying to help (freely of course :) ).
Doug|||> We tried to restore the backups
I assume this is backups done with the BACKUP DATABASE command?
> but it's asking for a file that
> doesn't exist.
Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
backups).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
> On Oct 8, 12:44 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> Basically, you will want to restore from your backup. Even if you find some hack to get this
>> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
>> new log file to be created but the reason it complains as it is is because SQL Server need the
>> log
>> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
>> might find will leave you with "half performed transactions" i.e., logically inconsistent data
>> (like
>> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
>> modifications against meta-data so you risk having a physical corruption as well.
> We tried to restore the backups, but it's asking for a file that
> doesn't exist.
> For example, we tell it to restore from Wednesday, but it asks for
> Friday also. Which doesn't exist.
> This isn't my machine directly but belongs to someone else that I'm
> trying to help (freely of course :) ).
> Doug
>|||On Oct 8, 2:59 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> > We tried to restore the backups
> I assume this is backups done with the BACKUP DATABASE command?
> > but it's asking for a file that
> > doesn't exist.
> Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
> backups).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>
> <nerd1...@.gmail.com> wrote in messagenews:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
> > On Oct 8, 12:44 pm, "Tibor Karaszi"
> > <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> >> Basically, you will want to restore from your backup. Even if you find some hack to get this
> >> database into SQL Server, your data is inconsistent. Whatever hack you might find will force some
> >> new log file to be created but the reason it complains as it is is because SQL Server need the
> >> log
> >> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack you
> >> might find will leave you with "half performed transactions" i.e., logically inconsistent data
> >> (like
> >> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
> >> modifications against meta-data so you risk having a physical corruption as well.
We tried doing the restore through the enterprise manager.
Yes, this was done with the SQL backup manager.
> > We tried to restore the backups, but it's asking for a file that
> > doesn't exist.
> > For example, we tell it to restore from Wednesday, but it asks for
> > Friday also. Which doesn't exist.
> > This isn't my machine directly but belongs to someone else that I'm
> > trying to help (freely of course :) ).
> > Doug- Hide quoted text -
> - Show quoted text -|||> We tried doing the restore through the enterprise manager.
Try the RESTORE command instead. You never know what a GUI tool want to do, and it is also easier to
communicate commands and error messages this way.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nerd1701@.gmail.com> wrote in message news:1191870417.832070.317830@.19g2000hsx.googlegroups.com...
> On Oct 8, 2:59 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> > We tried to restore the backups
>> I assume this is backups done with the BACKUP DATABASE command?
>> > but it's asking for a file that
>> > doesn't exist.
>> Who is "it"? Use the RESTORE DATABASE command and possibly RESTORE LOG (if you also have log
>> backups).
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>>
>> <nerd1...@.gmail.com> wrote in
>> messagenews:1191868968.424106.134380@.k79g2000hse.googlegroups.com...
>> > On Oct 8, 12:44 pm, "Tibor Karaszi"
>> > <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> >> Basically, you will want to restore from your backup. Even if you find some hack to get this
>> >> database into SQL Server, your data is inconsistent. Whatever hack you might find will force
>> >> some
>> >> new log file to be created but the reason it complains as it is is because SQL Server need the
>> >> log
>> >> file to do REDO and UNDO for transactions in order to get a consistent database. So the hack
>> >> you
>> >> might find will leave you with "half performed transactions" i.e., logically inconsistent data
>> >> (like
>> >> an order for a customer that doesn't exist). SQL Server also uses transactions to protect
>> >> modifications against meta-data so you risk having a physical corruption as well.
> We tried doing the restore through the enterprise manager.
> Yes, this was done with the SQL backup manager.
>> > We tried to restore the backups, but it's asking for a file that
>> > doesn't exist.
>> > For example, we tell it to restore from Wednesday, but it asks for
>> > Friday also. Which doesn't exist.
>> > This isn't my machine directly but belongs to someone else that I'm
>> > trying to help (freely of course :) ).
>> > Doug- Hide quoted text -
>> - Show quoted text -
>sql

Have an .mdf file but can't seem to attach it.

We had a server that was having all kinds of problems. We finally got it
booted and I copied the .MDF file off the hard drive. I'm trying to create a
new database on a different machine using this .MDF file and it appears to
not work. I had shut down SQL on the machine before I copied the file but I
didn't detach it ( didn't have the time and I was trying to explain it to
somebody else. ) So now I have this .MDF file that I can't attach. I'm doing
the following command:
use master
go
CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
Server\MSSQL\Data\BugTracking.mdf') for attach
go
and I'm getting the following error:
Msg 1813, Level 16, State 2, Line 1
Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
Msg 602, Level 21, State 50, Line 1
Could not find row in sysindexes for database ID 23, object ID 1, index ID
1. Run DBCC CHECKTABLE on sysindexes.
I've also tried to a direct attach deleting the log file and it won't do it.
Anybody have any thoughts?
TIA - Jeff.
Can you try sp_attach_single_file_db and see if it works?
See:
http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx

Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Mufasa" <jb@.nowhere.com> wrote in message
news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
> We had a server that was having all kinds of problems. We finally got it
> booted and I copied the .MDF file off the hard drive. I'm trying to create
> a new database on a different machine using this .MDF file and it appears
> to not work. I had shut down SQL on the machine before I copied the file
> but I didn't detach it ( didn't have the time and I was trying to explain
> it to somebody else. ) So now I have this .MDF file that I can't attach.
> I'm doing the following command:
>
> use master
> go
> CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\BugTracking.mdf') for attach
> go
>
> and I'm getting the following error:
>
> Msg 1813, Level 16, State 2, Line 1
> Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
> Msg 602, Level 21, State 50, Line 1
> Could not find row in sysindexes for database ID 23, object ID 1, index ID
> 1. Run DBCC CHECKTABLE on sysindexes.
>
> I've also tried to a direct attach deleting the log file and it won't do
> it.
> Anybody have any thoughts?
> TIA - Jeff.
>
|||Sorry everybody - I finally figured out what was wrong - I was trying to
attach the file from a 2005 db into 2000. Once I switched to another server,
it worked fine.
J.
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:E95832E9-C1D4-4BC3-B010-6F7079F2AEAF@.microsoft.com...
> Can you try sp_attach_single_file_db and see if it works?
> See:
> http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Mufasa" <jb@.nowhere.com> wrote in message
> news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
>

Have an .mdf file but can't seem to attach it.

We had a server that was having all kinds of problems. We finally got it
booted and I copied the .MDF file off the hard drive. I'm trying to create a
new database on a different machine using this .MDF file and it appears to
not work. I had shut down SQL on the machine before I copied the file but I
didn't detach it ( didn't have the time and I was trying to explain it to
somebody else. ) So now I have this .MDF file that I can't attach. I'm doing
the following command:
use master
go
CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
Server\MSSQL\Data\BugTracking.mdf') for attach
go
and I'm getting the following error:
Msg 1813, Level 16, State 2, Line 1
Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
Msg 602, Level 21, State 50, Line 1
Could not find row in sysindexes for database ID 23, object ID 1, index ID
1. Run DBCC CHECKTABLE on sysindexes.
I've also tried to a direct attach deleting the log file and it won't do it.
Anybody have any thoughts?
TIA - Jeff.Can you try sp_attach_single_file_db and see if it works?
See:
http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx
Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Mufasa" <jb@.nowhere.com> wrote in message
news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
> We had a server that was having all kinds of problems. We finally got it
> booted and I copied the .MDF file off the hard drive. I'm trying to create
> a new database on a different machine using this .MDF file and it appears
> to not work. I had shut down SQL on the machine before I copied the file
> but I didn't detach it ( didn't have the time and I was trying to explain
> it to somebody else. ) So now I have this .MDF file that I can't attach.
> I'm doing the following command:
>
> use master
> go
> CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\BugTracking.mdf') for attach
> go
>
> and I'm getting the following error:
>
> Msg 1813, Level 16, State 2, Line 1
> Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
> Msg 602, Level 21, State 50, Line 1
> Could not find row in sysindexes for database ID 23, object ID 1, index ID
> 1. Run DBCC CHECKTABLE on sysindexes.
>
> I've also tried to a direct attach deleting the log file and it won't do
> it.
> Anybody have any thoughts?
> TIA - Jeff.
>|||Sorry everybody - I finally figured out what was wrong - I was trying to
attach the file from a 2005 db into 2000. Once I switched to another server,
it worked fine.
J.
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:E95832E9-C1D4-4BC3-B010-6F7079F2AEAF@.microsoft.com...
> Can you try sp_attach_single_file_db and see if it works?
> See:
> http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Mufasa" <jb@.nowhere.com> wrote in message
> news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
>

Have an .mdf file but can't seem to attach it.

We had a server that was having all kinds of problems. We finally got it
booted and I copied the .MDF file off the hard drive. I'm trying to create a
new database on a different machine using this .MDF file and it appears to
not work. I had shut down SQL on the machine before I copied the file but I
didn't detach it ( didn't have the time and I was trying to explain it to
somebody else. ) So now I have this .MDF file that I can't attach. I'm doing
the following command:
use master
go
CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
Server\MSSQL\Data\BugTracking.mdf') for attach
go
and I'm getting the following error:
Msg 1813, Level 16, State 2, Line 1
Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
Msg 602, Level 21, State 50, Line 1
Could not find row in sysindexes for database ID 23, object ID 1, index ID
1. Run DBCC CHECKTABLE on sysindexes.
I've also tried to a direct attach deleting the log file and it won't do it.
Anybody have any thoughts?
TIA - Jeff.Can you try sp_attach_single_file_db and see if it works?
See:
http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx
Adam Machanic
SQL Server MVP
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Mufasa" <jb@.nowhere.com> wrote in message
news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
> We had a server that was having all kinds of problems. We finally got it
> booted and I copied the .MDF file off the hard drive. I'm trying to create
> a new database on a different machine using this .MDF file and it appears
> to not work. I had shut down SQL on the machine before I copied the file
> but I didn't detach it ( didn't have the time and I was trying to explain
> it to somebody else. ) So now I have this .MDF file that I can't attach.
> I'm doing the following command:
>
> use master
> go
> CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\BugTracking.mdf') for attach
> go
>
> and I'm getting the following error:
>
> Msg 1813, Level 16, State 2, Line 1
> Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
> Msg 602, Level 21, State 50, Line 1
> Could not find row in sysindexes for database ID 23, object ID 1, index ID
> 1. Run DBCC CHECKTABLE on sysindexes.
>
> I've also tried to a direct attach deleting the log file and it won't do
> it.
> Anybody have any thoughts?
> TIA - Jeff.
>|||Sorry everybody - I finally figured out what was wrong - I was trying to
attach the file from a 2005 db into 2000. Once I switched to another server,
it worked fine.
J.
"Adam Machanic" <amachanic@.IHATESPAMgmail.com> wrote in message
news:E95832E9-C1D4-4BC3-B010-6F7079F2AEAF@.microsoft.com...
> Can you try sp_attach_single_file_db and see if it works?
> See:
> http://msdn2.microsoft.com/en-us/library/ms174385(SQL.90).aspx
>
> --
> Adam Machanic
> SQL Server MVP
> Author, "Expert SQL Server 2005 Development"
> http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "Mufasa" <jb@.nowhere.com> wrote in message
> news:eH$ODo1sHHA.840@.TK2MSFTNGP03.phx.gbl...
>> We had a server that was having all kinds of problems. We finally got it
>> booted and I copied the .MDF file off the hard drive. I'm trying to
>> create a new database on a different machine using this .MDF file and it
>> appears to not work. I had shut down SQL on the machine before I copied
>> the file but I didn't detach it ( didn't have the time and I was trying
>> to explain it to somebody else. ) So now I have this .MDF file that I
>> can't attach. I'm doing the following command:
>>
>> use master
>> go
>> CREATE DATABASE BugTracking on (Filename='D:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\BugTracking.mdf') for attach
>> go
>>
>> and I'm getting the following error:
>>
>> Msg 1813, Level 16, State 2, Line 1
>> Could not open new database 'BugTracking'. CREATE DATABASE is aborted.
>> Msg 602, Level 21, State 50, Line 1
>> Could not find row in sysindexes for database ID 23, object ID 1, index
>> ID 1. Run DBCC CHECKTABLE on sysindexes.
>>
>> I've also tried to a direct attach deleting the log file and it won't do
>> it.
>> Anybody have any thoughts?
>> TIA - Jeff.
>>
>

Have a copy of a database

Hi
Is any way of making a copy of a database (copying the MDF and LDF files)
without detaching the database?
Thanks
Yuelin
Yes. Use the BACKUP DATABASE command. This will after you have performed RESTORE achieve the same
effect as copying the physical files.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files) without detaching the
> database?
> Thanks
> Yuelin
>
|||You may use DTS to transfer data across. from em, right click the database,
import or export.
my 2c
Yifei
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files)
> without detaching the database?
> Thanks
> Yuelin
>
sql

Have a copy of a database

Hi
Is any way of making a copy of a database (copying the MDF and LDF files)
without detaching the database?
Thanks
YuelinYes. Use the BACKUP DATABASE command. This will after you have performed RES
TORE achieve the same
effect as copying the physical files.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files)
without detaching the
> database?
> Thanks
> Yuelin
>|||You may use DTS to transfer data across. from em, right click the database,
import or export.
my 2c
Yifei
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files)
> without detaching the database?
> Thanks
> Yuelin
>

Have a copy of a database

Hi
Is any way of making a copy of a database (copying the MDF and LDF files)
without detaching the database?
Thanks
YuelinYes. Use the BACKUP DATABASE command. This will after you have performed RESTORE achieve the same
effect as copying the physical files.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files) without detaching the
> database?
> Thanks
> Yuelin
>|||You may use DTS to transfer data across. from em, right click the database,
import or export.
my 2c
Yifei
"Yuelin Liang" <yuelinliang@.hotmail.com> wrote in message
news:O1MSAHZHFHA.3332@.TK2MSFTNGP15.phx.gbl...
> Hi
> Is any way of making a copy of a database (copying the MDF and LDF files)
> without detaching the database?
> Thanks
> Yuelin
>

Hard Drive Crashed. master & user db mdf & ldf files lost

Hello.

One of our hard drives has crashed and as a result we have lost our master mdf/ldf & user db mdf/ldf files. It's not that a critical system by any means, but if the hard drive crashes and the master mdf/ldf files & user db mdf/ldf are lost, is there any way of restoring the system?

I'm thinking we probably need to re-install Enterprise Manager completely, and re-install the user db from a backup.

Any advice/suggestions would be much appreciated.

Thanks in advance,If the disks are toast, then you have to restore from your backups. When you have the hardware and O/S back to where they need to be, install SQL Server with any required service packs/patches, then restore the master database (see BOL for instructions), then restore the user databases.

Hard drive crashed but MDF/LDF on drive D:

SQL 7.0/Server 2000
The c: drive crashed;
the MDF and LDF files were on drive D:
When a new hard drive is installed with the new OS and
SQL 7.0 installed on it...is there a way to "attach" to
the MDF and LDF files? or are they lost?
Thanks,
Don
with SQL7 and/or SQL 2000
you can try sp_attach_db
PS. usually better to perform sp_detach_db but you had no choice in this
instance :-)
hope this works.
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>
|||sp_attach_db is the first choice but if you have issues this may help:
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>

Hard drive crashed but MDF/LDF on drive D:

SQL 7.0/Server 2000
The c: drive crashed;
the MDF and LDF files were on drive D:
When a new hard drive is installed with the new OS and
SQL 7.0 installed on it...is there a way to "attach" to
the MDF and LDF files? or are they lost?
Thanks,
Donwith SQL7 and/or SQL 2000
you can try sp_attach_db
PS. usually better to perform sp_detach_db but you had no choice in this
instance :-)
hope this works.
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>|||sp_attach_db is the first choice but if you have issues this may help:
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>

Hard drive crashed but MDF/LDF on drive D:

SQL 7.0/Server 2000
The c: drive crashed;
the MDF and LDF files were on drive D:
When a new hard drive is installed with the new OS and
SQL 7.0 installed on it...is there a way to "attach" to
the MDF and LDF files? or are they lost?
Thanks,
Donwith SQL7 and/or SQL 2000
you can try sp_attach_db
PS. usually better to perform sp_detach_db but you had no choice in this
instance :-)
hope this works.
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>|||sp_attach_db is the first choice but if you have issues this may help:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Don" <anonymous@.discussions.microsoft.com> wrote in message
news:086001c4f832$20813b50$a601280a@.phx.gbl...
> SQL 7.0/Server 2000
> The c: drive crashed;
> the MDF and LDF files were on drive D:
> When a new hard drive is installed with the new OS and
> SQL 7.0 installed on it...is there a way to "attach" to
> the MDF and LDF files? or are they lost?
> Thanks,
> Don
>