I cant bring my database online since the LDF is missing. However, the MDF
is fine. If I try to bring it online I get an error 5181 due to the missing
file.
Is there anyway to get the database going again without the transaction log?
Cheers,
elzikoHi,
Start the database in Emergency mode. So that Database will be started with
out transaction log. After that you can use DTS to transfer the data
and objects to a new database.
How to start the database in Emergency Mode:
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768
where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
Note:
Setting the database status to emergency mode tells SQL Server to skip
automatic recovery and
lets you access the data.
Thanks
Hari
MCDBA
"elziko" <elziko@.NOTSPAMMINGyahoo.co.uk> wrote in message
news:u6nrn1kEEHA.1368@.TK2MSFTNGP11.phx.gbl...
> I cant bring my database online since the LDF is missing. However, the MDF
> is fine. If I try to bring it online I get an error 5181 due to the
missing
> file.
> Is there anyway to get the database going again without the transaction
log?
> --
> Cheers,
> elziko
>
Showing posts with label ldf. Show all posts
Showing posts with label ldf. Show all posts
Thursday, February 16, 2012
Bring Log File (LDF) Online
Hi,
I have a server with two separate paritions running SQL 2005. One partition
with the data (mdf) files failed entirely and all data was lost. The second
partition with the log (ldf) files remained entact.
One of the failed databases was restored from tape, but it's not recent
enough. I want to make the database "see" the log file. How can I make a
SQL database recongize a more recent log file?
Once the database/log file are both online, then I can hopefully analyze the
log file using third party tools (ie: Apex or Lumigent) to retrieve data.
Thanks in advance.Hi Dennis
You can't see the log as such, the restored database would have it's own log
file. If your database is in full recovery mode and you have log backups,
they could be rolled forward
http://msdn2.microsoft.com/en-us/library/ms189596.aspx although if you have
not backed up the tail log it will not be up to the point of failure
http://msdn2.microsoft.com/en-us/library/ms179314.aspx
John
"Dennis Grecu" <Dennis Grecu@.discussions.microsoft.com> wrote in message
news:728FC0C4-B069-40F6-A874-96265D0FF4FE@.microsoft.com...
> Hi,
> I have a server with two separate paritions running SQL 2005. One
> partition
> with the data (mdf) files failed entirely and all data was lost. The
> second
> partition with the log (ldf) files remained entact.
> One of the failed databases was restored from tape, but it's not recent
> enough. I want to make the database "see" the log file. How can I make a
> SQL database recongize a more recent log file?
> Once the database/log file are both online, then I can hopefully analyze
> the
> log file using third party tools (ie: Apex or Lumigent) to retrieve data.
> Thanks in advance.
>
I have a server with two separate paritions running SQL 2005. One partition
with the data (mdf) files failed entirely and all data was lost. The second
partition with the log (ldf) files remained entact.
One of the failed databases was restored from tape, but it's not recent
enough. I want to make the database "see" the log file. How can I make a
SQL database recongize a more recent log file?
Once the database/log file are both online, then I can hopefully analyze the
log file using third party tools (ie: Apex or Lumigent) to retrieve data.
Thanks in advance.Hi Dennis
You can't see the log as such, the restored database would have it's own log
file. If your database is in full recovery mode and you have log backups,
they could be rolled forward
http://msdn2.microsoft.com/en-us/library/ms189596.aspx although if you have
not backed up the tail log it will not be up to the point of failure
http://msdn2.microsoft.com/en-us/library/ms179314.aspx
John
"Dennis Grecu" <Dennis Grecu@.discussions.microsoft.com> wrote in message
news:728FC0C4-B069-40F6-A874-96265D0FF4FE@.microsoft.com...
> Hi,
> I have a server with two separate paritions running SQL 2005. One
> partition
> with the data (mdf) files failed entirely and all data was lost. The
> second
> partition with the log (ldf) files remained entact.
> One of the failed databases was restored from tape, but it's not recent
> enough. I want to make the database "see" the log file. How can I make a
> SQL database recongize a more recent log file?
> Once the database/log file are both online, then I can hopefully analyze
> the
> log file using third party tools (ie: Apex or Lumigent) to retrieve data.
> Thanks in advance.
>
Bring Log File (LDF) Online
Hi,
I have a server with two separate paritions running SQL 2005. One partition
with the data (mdf) files failed entirely and all data was lost. The second
partition with the log (ldf) files remained entact.
One of the failed databases was restored from tape, but it's not recent
enough. I want to make the database "see" the log file. How can I make a
SQL database recongize a more recent log file?
Once the database/log file are both online, then I can hopefully analyze the
log file using third party tools (ie: Apex or Lumigent) to retrieve data.
Thanks in advance.Hi Dennis
You can't see the log as such, the restored database would have it's own log
file. If your database is in full recovery mode and you have log backups,
they could be rolled forward
http://msdn2.microsoft.com/en-us/library/ms189596.aspx although if you have
not backed up the tail log it will not be up to the point of failure
http://msdn2.microsoft.com/en-us/library/ms179314.aspx
John
"Dennis Grecu" <Dennis Grecu@.discussions.microsoft.com> wrote in message
news:728FC0C4-B069-40F6-A874-96265D0FF4FE@.microsoft.com...
> Hi,
> I have a server with two separate paritions running SQL 2005. One
> partition
> with the data (mdf) files failed entirely and all data was lost. The
> second
> partition with the log (ldf) files remained entact.
> One of the failed databases was restored from tape, but it's not recent
> enough. I want to make the database "see" the log file. How can I make a
> SQL database recongize a more recent log file?
> Once the database/log file are both online, then I can hopefully analyze
> the
> log file using third party tools (ie: Apex or Lumigent) to retrieve data.
> Thanks in advance.
>
I have a server with two separate paritions running SQL 2005. One partition
with the data (mdf) files failed entirely and all data was lost. The second
partition with the log (ldf) files remained entact.
One of the failed databases was restored from tape, but it's not recent
enough. I want to make the database "see" the log file. How can I make a
SQL database recongize a more recent log file?
Once the database/log file are both online, then I can hopefully analyze the
log file using third party tools (ie: Apex or Lumigent) to retrieve data.
Thanks in advance.Hi Dennis
You can't see the log as such, the restored database would have it's own log
file. If your database is in full recovery mode and you have log backups,
they could be rolled forward
http://msdn2.microsoft.com/en-us/library/ms189596.aspx although if you have
not backed up the tail log it will not be up to the point of failure
http://msdn2.microsoft.com/en-us/library/ms179314.aspx
John
"Dennis Grecu" <Dennis Grecu@.discussions.microsoft.com> wrote in message
news:728FC0C4-B069-40F6-A874-96265D0FF4FE@.microsoft.com...
> Hi,
> I have a server with two separate paritions running SQL 2005. One
> partition
> with the data (mdf) files failed entirely and all data was lost. The
> second
> partition with the log (ldf) files remained entact.
> One of the failed databases was restored from tape, but it's not recent
> enough. I want to make the database "see" the log file. How can I make a
> SQL database recongize a more recent log file?
> Once the database/log file are both online, then I can hopefully analyze
> the
> log file using third party tools (ie: Apex or Lumigent) to retrieve data.
> Thanks in advance.
>
Subscribe to:
Posts (Atom)