Having a problem attaching a database

My SQL Server crashed back in August. I was able to recover some of the data
but it was not worth using. I was better off just starting over from
scratch. However, I did save the recovered information in case I needed to
pull any of it for reference. Well, that is what I need to do and I am
having trouble attaching the database to pull the required information. I am
very green when it comes to this stuff. I am running SQL Server 2000 v5, SP4
on Windows 2000. Below are the steps that I have taken to try to retrieve
the information:
1. Copy the recovered database to a different drive and rename it to
eliminate any possibility of over-writing my current database information
2. Open SQL Server Enterprise Manager
3. Attach Database
4. Select the database that I want to attach (renamed file in new location)
5. I have to rename the "Current file(s) location" to the correct file name
for the mdf and ldf files. The ldf file is still not recognized because the
file does not exist and will be created when attached.
6. I change the "Attach as:" to match the file name and assign the
appropriate owner.
7. Click OK and a message appears asking if I want to create an ldf file.
8. I click Yes to have the file created and an error message pops up:
Error 5105: Device activation error. The physical file
'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect.
Plant1_Shreve is on drive E. The F drive is the location of the current
database files.
9. I click OK and another window pops up stating "Attach database has
failed". I click OK to this and I am back where I started
Please try sp_attach_db in "Query Analyzer" and see what happens.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"M Figy" <M Figy@.discussions.microsoft.com> wrote in message
news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> My SQL Server crashed back in August. I was able to recover some of the
> data
> but it was not worth using. I was better off just starting over from
> scratch. However, I did save the recovered information in case I needed
> to
> pull any of it for reference. Well, that is what I need to do and I am
> having trouble attaching the database to pull the required information. I
> am
> very green when it comes to this stuff. I am running SQL Server 2000 v5,
> SP4
> on Windows 2000. Below are the steps that I have taken to try to retrieve
> the information:
> 1. Copy the recovered database to a different drive and rename it to
> eliminate any possibility of over-writing my current database information
> 2. Open SQL Server Enterprise Manager
> 3. Attach Database
> 4. Select the database that I want to attach (renamed file in new
> location)
> 5. I have to rename the "Current file(s) location" to the correct file
> name
> for the mdf and ldf files. The ldf file is still not recognized because
> the
> file does not exist and will be created when attached.
> 6. I change the "Attach as:" to match the file name and assign the
> appropriate owner.
> 7. Click OK and a message appears asking if I want to create an ldf file.
> 8. I click Yes to have the file created and an error message pops up:
> Error 5105: Device activation error. The physical file
> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
> database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
> incorrect.
> Plant1_Shreve is on drive E. The F drive is the location of the current
> database files.
> 9. I click OK and another window pops up stating "Attach database has
> failed". I click OK to this and I am back where I started
|||Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
same results as before. The syntax that I used follows:
EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
@.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
Did I do this right?
"wei xiao [MSFT]" wrote:

> Please try sp_attach_db in "Query Analyzer" and see what happens.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "M Figy" <M Figy@.discussions.microsoft.com> wrote in message
> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
>
>
|||Hi There,
You need to try using sp_attach_single_file_db (see BOL)
This allows the attaching of just the MDF file and creates a new Log file
for your DB.
HTH,
Cheers,
Des
On 24/11/2004 14:05, in article
D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
Figy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
> same results as before. The syntax that I used follows:
> EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
> @.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
> Did I do this right?
> "wei xiao [MSFT]" wrote:
|||I really appreciate everyone's help but I am still getting the same error
message that refers back to the file PRODUCTION_Log.LDF. Let me try to make
my request as simple as possible. I apologize for my ignorance. I am try to
recover data from a database that was corrupted due to the server crashing.
Some of the corrupt data was recovered and the database files were stored in
another location. I want to pull this recovered data into a database with a
different name so that I do not risk overwriting any current information. I
need some detailed instruction on how to do this, if it is possible. Please
do not hesitate to ask me any questions to gather as much info that you may
need. If it may be easier, we can communicate via e-mail:
mfigy@.wauseonmachine.com
Thank you very much for your anticipated help. Mike
"Des FitzGerald" wrote:

> Hi There,
> You need to try using sp_attach_single_file_db (see BOL)
> This allows the attaching of just the MDF file and creates a new Log file
> for your DB.
> HTH,
> Cheers,
> Des
>
> On 24/11/2004 14:05, in article
> D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
> Figy@.discussions.microsoft.com> wrote:
>
>
|||"M Figy" <MFigy@.discussions.microsoft.com> wrote in message
news:DBBF9AEA-54C0-4BB4-8FDE-1DAE25623175@.microsoft.com...
> I really appreciate everyone's help but I am still getting the same error
> message that refers back to the file PRODUCTION_Log.LDF. Let me try to
make
> my request as simple as possible. I apologize for my ignorance. I am try
to
> recover data from a database that was corrupted due to the server
crashing.
> Some of the corrupt data was recovered and the database files were stored
in
> another location. I want to pull this recovered data into a database with
a
> different name so that I do not risk overwriting any current information.
I
> need some detailed instruction on how to do this, if it is possible.
Please
> do not hesitate to ask me any questions to gather as much info that you
may
> need. If it may be easier, we can communicate via e-mail:
> mfigy@.wauseonmachine.com
The reality is.. you may not be able to attach the corrupted databases.
Your best bet is to call Microsoft Server Support with Credit Card in hand.
They have a few tricks that MAY get your DB back.

Having a problem attaching a database

My SQL Server crashed back in August. I was able to recover some of the data
but it was not worth using. I was better off just starting over from
scratch. However, I did save the recovered information in case I needed to
pull any of it for reference. Well, that is what I need to do and I am
having trouble attaching the database to pull the required information. I am
very green when it comes to this stuff. I am running SQL Server 2000 v5, SP4
on Windows 2000. Below are the steps that I have taken to try to retrieve
the information:
1. Copy the recovered database to a different drive and rename it to
eliminate any possibility of over-writing my current database information
2. Open SQL Server Enterprise Manager
3. Attach Database
4. Select the database that I want to attach (renamed file in new location)
5. I have to rename the "Current file(s) location" to the correct file name
for the mdf and ldf files. The ldf file is still not recognized because the
file does not exist and will be created when attached.
6. I change the "Attach as:" to match the file name and assign the
appropriate owner.
7. Click OK and a message appears asking if I want to create an ldf file.
8. I click Yes to have the file created and an error message pops up:
Error 5105: Device activation error. The physical file
'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect.
Plant1_Shreve is on drive E. The F drive is the location of the current
database files.
9. I click OK and another window pops up stating "Attach database has
failed". I click OK to this and I am back where I startedPlease try sp_attach_db in "Query Analyzer" and see what happens.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"M Figy" <M Figy@.discussions.microsoft.com> wrote in message
news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> My SQL Server crashed back in August. I was able to recover some of the
> data
> but it was not worth using. I was better off just starting over from
> scratch. However, I did save the recovered information in case I needed
> to
> pull any of it for reference. Well, that is what I need to do and I am
> having trouble attaching the database to pull the required information. I
> am
> very green when it comes to this stuff. I am running SQL Server 2000 v5,
> SP4
> on Windows 2000. Below are the steps that I have taken to try to retrieve
> the information:
> 1. Copy the recovered database to a different drive and rename it to
> eliminate any possibility of over-writing my current database information
> 2. Open SQL Server Enterprise Manager
> 3. Attach Database
> 4. Select the database that I want to attach (renamed file in new
> location)
> 5. I have to rename the "Current file(s) location" to the correct file
> name
> for the mdf and ldf files. The ldf file is still not recognized because
> the
> file does not exist and will be created when attached.
> 6. I change the "Attach as:" to match the file name and assign the
> appropriate owner.
> 7. Click OK and a message appears asking if I want to create an ldf file.
> 8. I click Yes to have the file created and an error message pops up:
> Error 5105: Device activation error. The physical file
> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
> database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
> incorrect.
> Plant1_Shreve is on drive E. The F drive is the location of the current
> database files.
> 9. I click OK and another window pops up stating "Attach database has
> failed". I click OK to this and I am back where I started|||Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
same results as before. The syntax that I used follows:
EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
@.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
Did I do this right?
"wei xiao [MSFT]" wrote:
> Please try sp_attach_db in "Query Analyzer" and see what happens.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "M Figy" <M Figy@.discussions.microsoft.com> wrote in message
> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> > My SQL Server crashed back in August. I was able to recover some of the
> > data
> > but it was not worth using. I was better off just starting over from
> > scratch. However, I did save the recovered information in case I needed
> > to
> > pull any of it for reference. Well, that is what I need to do and I am
> > having trouble attaching the database to pull the required information. I
> > am
> > very green when it comes to this stuff. I am running SQL Server 2000 v5,
> > SP4
> > on Windows 2000. Below are the steps that I have taken to try to retrieve
> > the information:
> >
> > 1. Copy the recovered database to a different drive and rename it to
> > eliminate any possibility of over-writing my current database information
> > 2. Open SQL Server Enterprise Manager
> > 3. Attach Database
> > 4. Select the database that I want to attach (renamed file in new
> > location)
> > 5. I have to rename the "Current file(s) location" to the correct file
> > name
> > for the mdf and ldf files. The ldf file is still not recognized because
> > the
> > file does not exist and will be created when attached.
> > 6. I change the "Attach as:" to match the file name and assign the
> > appropriate owner.
> > 7. Click OK and a message appears asking if I want to create an ldf file.
> > 8. I click Yes to have the file created and an error message pops up:
> >
> > Error 5105: Device activation error. The physical file
> > 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
> > database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
> > error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
> > incorrect.
> >
> > Plant1_Shreve is on drive E. The F drive is the location of the current
> > database files.
> >
> > 9. I click OK and another window pops up stating "Attach database has
> > failed". I click OK to this and I am back where I started
>
>|||> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3184150360_1248646
Content-type: text/plain;
charset="US-ASCII"
Content-transfer-encoding: 7bit
Hi There,
You need to try using sp_attach_single_file_db (see BOL)
This allows the attaching of just the MDF file and creates a new Log file
for your DB.
HTH,
Cheers,
Des
On 24/11/2004 14:05, in article
D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
Figy@.discussions.microsoft.com> wrote:
> Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
> same results as before. The syntax that I used follows:
> EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
> @.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
> Did I do this right?
> "wei xiao [MSFT]" wrote:
>> Please try sp_attach_db in "Query Analyzer" and see what happens.
>> --
>> Wei Xiao [MSFT]
>> SQL Server Storage Engine Development
>> http://weblogs.asp.net/weix
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> "M Figy" <M Figy@.discussions.microsoft.com> wrote in message
>> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
>> My SQL Server crashed back in August. I was able to recover some of the
>> data
>> but it was not worth using. I was better off just starting over from
>> scratch. However, I did save the recovered information in case I needed
>> to
>> pull any of it for reference. Well, that is what I need to do and I am
>> having trouble attaching the database to pull the required information. I
>> am
>> very green when it comes to this stuff. I am running SQL Server 2000 v5,
>> SP4
>> on Windows 2000. Below are the steps that I have taken to try to retrieve
>> the information:
>> 1. Copy the recovered database to a different drive and rename it to
>> eliminate any possibility of over-writing my current database information
>> 2. Open SQL Server Enterprise Manager
>> 3. Attach Database
>> 4. Select the database that I want to attach (renamed file in new
>> location)
>> 5. I have to rename the "Current file(s) location" to the correct file
>> name
>> for the mdf and ldf files. The ldf file is still not recognized because
>> the
>> file does not exist and will be created when attached.
>> 6. I change the "Attach as:" to match the file name and assign the
>> appropriate owner.
>> 7. Click OK and a message appears asking if I want to create an ldf file.
>> 8. I click Yes to have the file created and an error message pops up:
>> Error 5105: Device activation error. The physical file
>> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
>> database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
>> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
>> incorrect.
>> Plant1_Shreve is on drive E. The F drive is the location of the current
>> database files.
>> 9. I click OK and another window pops up stating "Attach database has
>> failed". I click OK to this and I am back where I started
>>
--B_3184150360_1248646
Content-type: text/html;
charset="US-ASCII"
Content-transfer-encoding: quoted-printable
&

---

Re: Having a problem attaching a database
Hi Th=ere,
You need to try using sp_attach_single_file_db (see BOL)
This allows the attaching of just the MDF file and creates a new Log file f=or your DB.
HTH,
Cheers,
Des
On 24/11/2004 14:05, in article D64E767D-2DDB-416B-8C77-9895131C7DC6@.micros=oft.com, "M Figy" wrote:
> Once I figured out how to use the sp_attach_db i=n Query Analyzer, I got the
> same results as before. The syntax that I used follows:
>
> EXEC sp_attach_db @.dbname =3D N'--Plant1_Shreve',
> @.filename1 =3D N'E:\Program Files\jobboss\--Plant1_Sh=reve.mdf'
>
> Did I do this right?
>
> "wei xiao [MSFT]" wrote:
>
> Please try sp_attach_db in "Quer=y Analyzer" and see what happens.
>>
>> --
>> Wei Xiao [MSFT]
>> SQL Server Storage Engine Development
>>http://weblogs.asp.net/weix<=/a>
>>
>> This posting is provided "AS IS" with no warranties, and= confers no rights.
>>
>> "M Figy" wrote =in message
>> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> My SQL Server crashed back in Aug=ust. I was able to recover some of the
>> data
>> but it was not worth using. I was better off just starti=ng over from
>> scratch. However, I did save the recovered information i=n case I needed
>> to
>> pull any of it for reference. Well, that is what I need =to do and I am
>> having trouble attaching the database to pull the required inf=ormation. I
>> am
>> very green when it comes to this stuff. I am running SQL= Server 2000 v5,
>> SP4
>> on Windows 2000. Below are the steps that I have taken t=o try to retrieve
>> the information:
>>
>> 1. Copy the recovered database to a different drive and rename= it to
>> eliminate any possibility of over-writing my current database =information
>> 2. Open SQL Server Enterprise Manager
>> 3. Attach Database
>> 4. Select the database that I want to attach (renamed file in =new
>> location)
>> 5. I have to rename the "Current file(s) location" t=o the correct file
>> name
>> for the mdf and ldf files. The ldf file is still not rec=ognized because
>> the
>> file does not exist and will be created when attached.
>> 6. I change the "Attach as:" to match the file name =and assign the
>> appropriate owner.
>> 7. Click OK and a message appears asking if I want to create a=n ldf file.
>> 8. I click Yes to have the file created and an error message p=ops up:
>>
>> Error 5105: Device activation error. The physical file
>> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could =not open new
>> database 'Plant1_Shreve'. CREATE DATABASE is aborted. &n=bsp;Device activation
>> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF'= may be
>> incorrect.
>>
>> Plant1_Shreve is on drive E. The F drive is the location= of the current
>> database files.
>>
>> 9. I click OK and another window pops up stating "Attach =database has
>> failed". I click OK to this and I am back where I s=tarted
>
>>
>>
--B_3184150360_1248646--|||I really appreciate everyone's help but I am still getting the same error
message that refers back to the file PRODUCTION_Log.LDF. Let me try to make
my request as simple as possible. I apologize for my ignorance. I am try to
recover data from a database that was corrupted due to the server crashing.
Some of the corrupt data was recovered and the database files were stored in
another location. I want to pull this recovered data into a database with a
different name so that I do not risk overwriting any current information. I
need some detailed instruction on how to do this, if it is possible. Please
do not hesitate to ask me any questions to gather as much info that you may
need. If it may be easier, we can communicate via e-mail:
mfigy@.wauseonmachine.com
Thank you very much for your anticipated help. Mike
"Des FitzGerald" wrote:
> Hi There,
> You need to try using sp_attach_single_file_db (see BOL)
> This allows the attaching of just the MDF file and creates a new Log file
> for your DB.
> HTH,
> Cheers,
> Des
>
> On 24/11/2004 14:05, in article
> D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
> Figy@.discussions.microsoft.com> wrote:
> > Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
> > same results as before. The syntax that I used follows:
> >
> > EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
> > @.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
> >
> > Did I do this right?
> >
> > "wei xiao [MSFT]" wrote:
> >
> >> Please try sp_attach_db in "Query Analyzer" and see what happens.
> >>
> >> --
> >> Wei Xiao [MSFT]
> >> SQL Server Storage Engine Development
> >> http://weblogs.asp.net/weix
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >> "M Figy" <M Figy@.discussions.microsoft.com> wrote in message
> >> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> >> My SQL Server crashed back in August. I was able to recover some of the
> >> data
> >> but it was not worth using. I was better off just starting over from
> >> scratch. However, I did save the recovered information in case I needed
> >> to
> >> pull any of it for reference. Well, that is what I need to do and I am
> >> having trouble attaching the database to pull the required information. I
> >> am
> >> very green when it comes to this stuff. I am running SQL Server 2000 v5,
> >> SP4
> >> on Windows 2000. Below are the steps that I have taken to try to retrieve
> >> the information:
> >>
> >> 1. Copy the recovered database to a different drive and rename it to
> >> eliminate any possibility of over-writing my current database information
> >> 2. Open SQL Server Enterprise Manager
> >> 3. Attach Database
> >> 4. Select the database that I want to attach (renamed file in new
> >> location)
> >> 5. I have to rename the "Current file(s) location" to the correct file
> >> name
> >> for the mdf and ldf files. The ldf file is still not recognized because
> >> the
> >> file does not exist and will be created when attached.
> >> 6. I change the "Attach as:" to match the file name and assign the
> >> appropriate owner.
> >> 7. Click OK and a message appears asking if I want to create an ldf file.
> >> 8. I click Yes to have the file created and an error message pops up:
> >>
> >> Error 5105: Device activation error. The physical file
> >> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
> >> database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
> >> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
> >> incorrect.
> >>
> >> Plant1_Shreve is on drive E. The F drive is the location of the current
> >> database files.
> >>
> >> 9. I click OK and another window pops up stating "Attach database has
> >> failed". I click OK to this and I am back where I started
> >>
> >>
> >>
>|||"M Figy" <MFigy@.discussions.microsoft.com> wrote in message
news:DBBF9AEA-54C0-4BB4-8FDE-1DAE25623175@.microsoft.com...
> I really appreciate everyone's help but I am still getting the same error
> message that refers back to the file PRODUCTION_Log.LDF. Let me try to
make
> my request as simple as possible. I apologize for my ignorance. I am try
to
> recover data from a database that was corrupted due to the server
crashing.
> Some of the corrupt data was recovered and the database files were stored
in
> another location. I want to pull this recovered data into a database with
a
> different name so that I do not risk overwriting any current information.
I
> need some detailed instruction on how to do this, if it is possible.
Please
> do not hesitate to ask me any questions to gather as much info that you
may
> need. If it may be easier, we can communicate via e-mail:
> mfigy@.wauseonmachine.com
The reality is.. you may not be able to attach the corrupted databases.
Your best bet is to call Microsoft Server Support with Credit Card in hand.
They have a few tricks that MAY get your DB back.

Having a problem attaching a database

My SQL Server crashed back in August. I was able to recover some of the dat
a
but it was not worth using. I was better off just starting over from
scratch. However, I did save the recovered information in case I needed to
pull any of it for reference. Well, that is what I need to do and I am
having trouble attaching the database to pull the required information. I a
m
very green when it comes to this stuff. I am running SQL Server 2000 v5, SP
4
on Windows 2000. Below are the steps that I have taken to try to retrieve
the information:
1. Copy the recovered database to a different drive and rename it to
eliminate any possibility of over-writing my current database information
2. Open SQL Server Enterprise Manager
3. Attach Database
4. Select the database that I want to attach (renamed file in new location)
5. I have to rename the "Current file(s) location" to the correct file name
for the mdf and ldf files. The ldf file is still not recognized because the
file does not exist and will be created when attached.
6. I change the "Attach as:" to match the file name and assign the
appropriate owner.
7. Click OK and a message appears asking if I want to create an ldf file.
8. I click Yes to have the file created and an error message pops up:
Error 5105: Device activation error. The physical file
'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect.
Plant1_Shreve is on drive E. The F drive is the location of the current
database files.
9. I click OK and another window pops up stating "Attach database has
failed". I click OK to this and I am back where I startedPlease try sp_attach_db in "Query Analyzer" and see what happens.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"M Figy" <M Figy@.discussions.microsoft.com> wrote in message
news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
> My SQL Server crashed back in August. I was able to recover some of the
> data
> but it was not worth using. I was better off just starting over from
> scratch. However, I did save the recovered information in case I needed
> to
> pull any of it for reference. Well, that is what I need to do and I am
> having trouble attaching the database to pull the required information. I
> am
> very green when it comes to this stuff. I am running SQL Server 2000 v5,
> SP4
> on Windows 2000. Below are the steps that I have taken to try to retrieve
> the information:
> 1. Copy the recovered database to a different drive and rename it to
> eliminate any possibility of over-writing my current database information
> 2. Open SQL Server Enterprise Manager
> 3. Attach Database
> 4. Select the database that I want to attach (renamed file in new
> location)
> 5. I have to rename the "Current file(s) location" to the correct file
> name
> for the mdf and ldf files. The ldf file is still not recognized because
> the
> file does not exist and will be created when attached.
> 6. I change the "Attach as:" to match the file name and assign the
> appropriate owner.
> 7. Click OK and a message appears asking if I want to create an ldf file.
> 8. I click Yes to have the file created and an error message pops up:
> Error 5105: Device activation error. The physical file
> 'F:\Jobboss\PRODUCTION_log.LDF' may be incorrect. Could not open new
> database 'Plant1_Shreve'. CREATE DATABASE is aborted. Device activation
> error. The physical file 'F:\Jobboss\PRODUCTION_log.LDF' may be
> incorrect.
> Plant1_Shreve is on drive E. The F drive is the location of the current
> database files.
> 9. I click OK and another window pops up stating "Attach database has
> failed". I click OK to this and I am back where I started|||Once I figured out how to use the sp_attach_db in Query Analyzer, I got the
same results as before. The syntax that I used follows:
EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
@.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
Did I do this right?
"wei xiao [MSFT]" wrote:

> Please try sp_attach_db in "Query Analyzer" and see what happens.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "M Figy" <M Figy@.discussions.microsoft.com> wrote in message
> news:85957AE4-6F99-4CA7-ADBE-E8FB534DD35D@.microsoft.com...
>
>|||Hi There,
You need to try using sp_attach_single_file_db (see BOL)
This allows the attaching of just the MDF file and creates a new Log file
for your DB.
HTH,
Cheers,
Des
On 24/11/2004 14:05, in article
D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
Figy@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Once I figured out how to use the sp_attach_db in Query Analyzer, I got th
e
> same results as before. The syntax that I used follows:
> EXEC sp_attach_db @.dbname = N'--Plant1_Shreve',
> @.filename1 = N'E:\Program Files\jobboss\--Plant1_Shreve.mdf'
> Did I do this right?
> "wei xiao [MSFT]" wrote:
>|||I really appreciate everyone's help but I am still getting the same error
message that refers back to the file PRODUCTION_Log.LDF. Let me try to make
my request as simple as possible. I apologize for my ignorance. I am try t
o
recover data from a database that was corrupted due to the server crashing.
Some of the corrupt data was recovered and the database files were stored in
another location. I want to pull this recovered data into a database with a
different name so that I do not risk overwriting any current information. I
need some detailed instruction on how to do this, if it is possible. Please
do not hesitate to ask me any questions to gather as much info that you may
need. If it may be easier, we can communicate via e-mail:
mfigy@.wauseonmachine.com
Thank you very much for your anticipated help. Mike
"Des FitzGerald" wrote:

> Hi There,
> You need to try using sp_attach_single_file_db (see BOL)
> This allows the attaching of just the MDF file and creates a new Log file
> for your DB.
> HTH,
> Cheers,
> Des
>
> On 24/11/2004 14:05, in article
> D64E767D-2DDB-416B-8C77-9895131C7DC6@.microsoft.com, "M Figy" <M
> Figy@.discussions.microsoft.com> wrote:
>
>|||"M Figy" <MFigy@.discussions.microsoft.com> wrote in message
news:DBBF9AEA-54C0-4BB4-8FDE-1DAE25623175@.microsoft.com...
> I really appreciate everyone's help but I am still getting the same error
> message that refers back to the file PRODUCTION_Log.LDF. Let me try to
make
> my request as simple as possible. I apologize for my ignorance. I am try
to
> recover data from a database that was corrupted due to the server
crashing.
> Some of the corrupt data was recovered and the database files were stored
in
> another location. I want to pull this recovered data into a database with
a
> different name so that I do not risk overwriting any current information.
I
> need some detailed instruction on how to do this, if it is possible.
Please
> do not hesitate to ask me any questions to gather as much info that you
may
> need. If it may be easier, we can communicate via e-mail:
> mfigy@.wauseonmachine.com
The reality is.. you may not be able to attach the corrupted databases.
Your best bet is to call Microsoft Server Support with Credit Card in hand.
They have a few tricks that MAY get your DB back.sql

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
>