[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 498
  • Last Modified:

How can I restore SQL 2005 database from Log Files?

I have a production database that was accidentally corrupted after my last backup. Tha backup is planned to backup the database every 20 days and it works fine.

I have restored the database to the last backup which is 15 days earlier and now need to restore the remaining data ftrom the lost 15 days.

I found a link said that I can restore that database using log files:

http://sqlserver2000.databases.aspfaq.com/how-do-i-recover-data-from-sql-server-s-log-files.html

But my SQL Server in 2005 not 200o

Any ideas?
0
Mohamed Khairy
Asked:
Mohamed Khairy
  • 6
  • 4
  • 3
  • +1
5 Solutions
 
pbarry1Commented:
Hi,

was your database in SIMPLE or FULL recovery mode?  

If your database was in SIMPLE recovery mode, you won't be able to recover the remaining days of data because SQL Server shrinks data on an ongoing basis.

If your database was in FULL recovery mode and you still have the original Log files, you can detach your database, copy the old Log files over the ones restored and reattach your database.  SQL Server should be able to reapply the remaining transactions.
0
 
QlemoC++ DeveloperCommented:
Above is true. You need to have setup Full or Bulk-Logged Recovery mode, and backed up all of the log files since your datafile backup. It's no different for 2000 or 2005 (or 2008).
0
 
ZberteocCommented:
If the database is in SIMPLE recovery mode your log files would be empty execpt for the last uncommitted transactions but you will not be able to recover nothing in between the last full backup and the uncommitted transactions I was talking above.

If you have log files from the last full backup that means you database was in FULL recovery mode and you are in luck.

The classic way to restore to the point in time of failure moment would be to restore the full backup first but make sure you choose WITH NO RECOVERY to let the database in restore mode to add the log files.

After that you will restore the log file but WITH RECOVERY option. If you have more than 1 log files you will have to restore them one by one in their chronological mode, still WITH NO RECOVERY option except for the very last log file which would be WITH RECOVERY mode.

I am not aware of the "trick' with detach and attached database. As I know you cannot attach a backup file but only a .MDB file(data file).
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Mohamed KhairyEnterprise Solutions ArchitectAuthor Commented:
Really appreciate your valuable comments.

I have a file named errorlog.6 and its size is 82 GB where the database is only 10 GB!!!

s that the log file needed or what?

0
 
QlemoC++ DeveloperCommented:
As the name says, it is the error log, not the transaction log. errorlog contains messages of MSSQL server while running (informational, warning and error).
0
 
Mohamed KhairyEnterprise Solutions ArchitectAuthor Commented:
@ Qlemo: The Database size is only 10 GB and the error log is 82 GB!!!!! is that normal?
0
 
QlemoC++ DeveloperCommented:
Not really. You should have look into it, and restart MSSQL so it creates a new log file.
0
 
ZberteocCommented:
Being so big means it hasn't been backed up fo a longer time, which is good if you intend to look into it. If you want to shrink it you don't have to restart just do a backup and then a log truncate. Another way is to change the recovery model of the database from Full to Simple, truncate the log file and then turn it back to Full recovery mode:

USE master
GO
-- set to simple recovery
ALTER DATABASE database_name
SET RECOVERY SIMPLE
GO
-- truncate log file
BACKUP LOG database_name WITH TRUNCATE_ONLY
GO
-- set back to full recovery
ALTER DATABASE database_name
SET RECOVERY FULL

However, in full recovery mode you need to perform periodic backups otherwise the log file will grow again.
0
 
QlemoC++ DeveloperCommented:
Zberteoc,
We are talking about the errlog.* files, not the transaction log.
0
 
ZberteocCommented:
Oh, sorry. Then just execute this:

EXEC sp_cycle_errorlog

will do the same to the error logs as the restart but without restarting. However this will probably not shrink the size.
0
 
QlemoC++ DeveloperCommented:
Good idea to use the that SP instead (learned something today ;-)). And no, the errlog will not get shrunk, because it contains important information.
0
 
Mohamed KhairyEnterprise Solutions ArchitectAuthor Commented:
I am a little bit confused now, can the error.log give me the missing data or only the root cause of  the problem?
0
 
QlemoC++ DeveloperCommented:
The errolog does not contain any data, only information like when MSSQL has been started, with which parameters, when backups happened - and most important if there are errors.
So no, you cannot get any data back from the errlog.
0
 
Mohamed KhairyEnterprise Solutions ArchitectAuthor Commented:
Thanks Guys, Unfortunately I can not restore the database but I've modified the backup plan and the recovery mode after read your valuable comments.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now