Rebuild .LDF File

I'm running SQL Server 2000, trying to rebuild a
transaction log since I only have an .MDF file. I've tried
creating a new database with the same name, stopping SQL
Server, then inserting the real data file, and setting the
database to emergency mode, then running the DBBC
Rebuild_Log('dbname', 'c:\somepath') and that command
appears to execute ok in Query Analyzer, but the log file
is not created. Is there any other method for attaching
the .mdf when you don't have the valid .ldf that goes with
it. (I've tried sp_attach_single_file) and that doesn't
work either. I get an error message that says it can't
find the log file (this db was pulled off of another
system that had the log file path stored pointed to
another drive). Any help is appreciated.
ThanksSounds like you have tried "sp_attach_single_file_db" (although this isn't
what you typed). This command to use to attach a database that only has a
the data file. I would review BOL and try this command again. Also is it
possible that you data file is corrupted?
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks|||If sp_attach_single_file doesn't work then see
http://www.nigelrivett.net/RecoverCorruptDatabase.html
"Steve" wrote:
> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks
>|||ok, that's what I meant, I didn't check the exact syntax,
but the "sp_attach_single_file_db" doesn't work... I don't
believe the .mdf data file is corrupted. All error
messages seem to point to the log file.
>--Original Message--
>Sounds like you have tried "sp_attach_single_file_db"
(although this isn't
>what you typed). This command to use to attach a
database that only has a
>the data file. I would review BOL and try this command
again. Also is it
>possible that you data file is corrupted?
>--
>----
--
>----
--
>-
>Need SQL Server Examples check out my website
>http://www.geocities.com/sqlserverexamples
>
>"Steve" <anonymous@.discussions.microsoft.com> wrote in
message
>news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
>> I'm running SQL Server 2000, trying to rebuild a
>> transaction log since I only have an .MDF file. I've
tried
>> creating a new database with the same name, stopping SQL
>> Server, then inserting the real data file, and setting
the
>> database to emergency mode, then running the DBBC
>> Rebuild_Log('dbname', 'c:\somepath') and that command
>> appears to execute ok in Query Analyzer, but the log
file
>> is not created. Is there any other method for attaching
>> the .mdf when you don't have the valid .ldf that goes
with
>> it. (I've tried sp_attach_single_file) and that doesn't
>> work either. I get an error message that says it can't
>> find the log file (this db was pulled off of another
>> system that had the log file path stored pointed to
>> another drive). Any help is appreciated.
>> Thanks
>
>.
>|||Hi Steve.
I have a feeling that the reason it didn't work is because
you did not detatch the database first using sp_detach_db,
though that is just a gut feeling.
Unfortunatly now you have a problem, anyway you have three
choices
1. Use Nigels very interesting and funky method to restore
it
2. Restore it from backup
3. Have a pretend nervous breakdown, take down your pants
and run from the office (be it slowly) screaming (that
SHOULD stop your boss from shouting at you).
nb if you have the original database try it again either
back it up, or try an sp_detatch_db.
Peter
"There is no such thing as public opinion. There is only
published opinion."
Winston Churchill
>--Original Message--
>I'm running SQL Server 2000, trying to rebuild a
>transaction log since I only have an .MDF file. I've
tried
>creating a new database with the same name, stopping SQL
>Server, then inserting the real data file, and setting
the
>database to emergency mode, then running the DBBC
>Rebuild_Log('dbname', 'c:\somepath') and that command
>appears to execute ok in Query Analyzer, but the log file
>is not created. Is there any other method for attaching
>the .mdf when you don't have the valid .ldf that goes
with
>it. (I've tried sp_attach_single_file) and that doesn't
>work either. I get an error message that says it can't
>find the log file (this db was pulled off of another
>system that had the log file path stored pointed to
>another drive). Any help is appreciated.
>Thanks
>.
>|||Ok, I just tried your instructions and it didn't work.
The database is in emergency mode, and I can't see any of
the tables, and when I try to setup a dts, I get an error
saying that it can't initialize the database.
>--Original Message--
>If sp_attach_single_file doesn't work then see
>http://www.nigelrivett.net/RecoverCorruptDatabase.html
>"Steve" wrote:
>> I'm running SQL Server 2000, trying to rebuild a
>> transaction log since I only have an .MDF file. I've
tried
>> creating a new database with the same name, stopping
SQL
>> Server, then inserting the real data file, and setting
the
>> database to emergency mode, then running the DBBC
>> Rebuild_Log('dbname', 'c:\somepath') and that command
>> appears to execute ok in Query Analyzer, but the log
file
>> is not created. Is there any other method for attaching
>> the .mdf when you don't have the valid .ldf that goes
with
>> it. (I've tried sp_attach_single_file) and that doesn't
>> work either. I get an error message that says it can't
>> find the log file (this db was pulled off of another
>> system that had the log file path stored pointed to
>> another drive). Any help is appreciated.
>> Thanks
>.
>|||I'll buy that... I received the file from a client, who
probably just did a standard detach through EM. I'll
probably have to resort to trying to get a hold of
the .BAK file. However I might pull the 3rd suggestion
just for fun.
Thanks
>--Original Message--
>Hi Steve.
>I have a feeling that the reason it didn't work is
because
>you did not detatch the database first using
sp_detach_db,
>though that is just a gut feeling.
>Unfortunatly now you have a problem, anyway you have
three
>choices
>1. Use Nigels very interesting and funky method to
restore
>it
>2. Restore it from backup
>3. Have a pretend nervous breakdown, take down your pants
>and run from the office (be it slowly) screaming (that
>SHOULD stop your boss from shouting at you).
>nb if you have the original database try it again either
>back it up, or try an sp_detatch_db.
>Peter
>"There is no such thing as public opinion. There is only
>published opinion."
>Winston Churchill
>
>>--Original Message--
>>I'm running SQL Server 2000, trying to rebuild a
>>transaction log since I only have an .MDF file. I've
>tried
>>creating a new database with the same name, stopping SQL
>>Server, then inserting the real data file, and setting
>the
>>database to emergency mode, then running the DBBC
>>Rebuild_Log('dbname', 'c:\somepath') and that command
>>appears to execute ok in Query Analyzer, but the log
file
>>is not created. Is there any other method for attaching
>>the .mdf when you don't have the valid .ldf that goes
>with
>>it. (I've tried sp_attach_single_file) and that doesn't
>>work either. I get an error message that says it can't
>>find the log file (this db was pulled off of another
>>system that had the log file path stored pointed to
>>another drive). Any help is appreciated.
>>Thanks
>>.
>.
>|||Other ways of stopping you boss from shouting at you
include superglue...
>--Original Message--
>I'll buy that... I received the file from a client, who
>probably just did a standard detach through EM. I'll
>probably have to resort to trying to get a hold of
>the .BAK file. However I might pull the 3rd suggestion
>just for fun.
>Thanks
>
>>--Original Message--
>>Hi Steve.
>>I have a feeling that the reason it didn't work is
>because
>>you did not detatch the database first using
>sp_detach_db,
>>though that is just a gut feeling.
>>Unfortunatly now you have a problem, anyway you have
>three
>>choices
>>1. Use Nigels very interesting and funky method to
>restore
>>it
>>2. Restore it from backup
>>3. Have a pretend nervous breakdown, take down your
pants
>>and run from the office (be it slowly) screaming (that
>>SHOULD stop your boss from shouting at you).
>>nb if you have the original database try it again either
>>back it up, or try an sp_detatch_db.
>>Peter
>>"There is no such thing as public opinion. There is only
>>published opinion."
>>Winston Churchill
>>
>>--Original Message--
>>I'm running SQL Server 2000, trying to rebuild a
>>transaction log since I only have an .MDF file. I've
>>tried
>>creating a new database with the same name, stopping
SQL
>>Server, then inserting the real data file, and setting
>>the
>>database to emergency mode, then running the DBBC
>>Rebuild_Log('dbname', 'c:\somepath') and that command
>>appears to execute ok in Query Analyzer, but the log
>file
>>is not created. Is there any other method for attaching
>>the .mdf when you don't have the valid .ldf that goes
>>with
>>it. (I've tried sp_attach_single_file) and that doesn't
>>work either. I get an error message that says it can't
>>find the log file (this db was pulled off of another
>>system that had the log file path stored pointed to
>>another drive). Any help is appreciated.
>>Thanks
>>.
>>.
>.
>