SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Point in time recovery
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

vijayasarathi
Starting Member

India
2 Posts

Posted - 06/20/2010 :  06:13:40  Show Profile  Reply with Quote
Point in time recovery

Problem: Whenever the database is corrupted due to any problem like hardware issue, or due to some heavy insertion of data in to the database which actually made some data corruption... and database went to suspect mode... of course we can make to emergency and copy the objects to another database in order to bring the data back in many cases. Think about the situation of data corruption and the databases are offline and no0t able to bring back ?

Solution:
Without backup , we cannot bring the data back..
1. First Check whether you have backup or not.
2. let say we have full backup and 4 sequesnce of log bakcup
3. Before restoring the database from the bakcup , we should make sure that the database is in full recovery mode (used for point in time recovery)
4. you should take tail backup for the corrupted database- which is used to take the data which are currently presents in the ldf file..
5. now we can start to restore the latest full backup with no recovery option
6. restore all the log backup by sequence with no recovery option
7. finally tail log backup have to restore -- this is last step which will bring all the data till the time the database corrupted.
8. Now we have uptodate data back.... :)


Vijayasarathi Dharmaraj

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 06/20/2010 :  06:50:14  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Is there a question here?

--
Gail Shaw
SQL Server MVP
Go to Top of Page

Kristen
Test

United Kingdom
22403 Posts

Posted - 06/20/2010 :  07:19:27  Show Profile  Reply with Quote
"due to some heavy insertion of data in to the database which actually made some data corruption"

Something wrong with your system if that happens ... unless you were meaning that you were doing bulk import without transaction and it failed half way through, and to repeat the bulk import you want to restore-and-repeat
Go to Top of Page

vijayasarathi
Starting Member

India
2 Posts

Posted - 06/20/2010 :  10:48:34  Show Profile  Reply with Quote
quote:
Originally posted by GilaMonster

Is there a question here?

--
Gail Shaw
SQL Server MVP



Hi Gail..I just explained the point in time recovery operation.. This is from my experience...Hope this can help some DBA's

Vijayasarathi Dharmaraj
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 06/20/2010 :  11:27:00  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
quote:
Originally posted by Kristen

"due to some heavy insertion of data in to the database which actually made some data corruption"

Something wrong with your system if that happens


Indeed. Heavy inserts (or any other form of usage for that matter) does not cause data corruption. Misbehaving IO subsystems cause data corruption.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

sks198117
Starting Member

India
46 Posts

Posted - 09/17/2010 :  10:54:10  Show Profile  Reply with Quote
Agreed with Gail ...I have never found data corruption due to heavy or rapid data insert it might cause system goes busy but i don't think database would be corrupt..If i am not wrong.

Thanks

---Thanks---
Santosh
Go to Top of Page

vaddesuresh
Starting Member

India
5 Posts

Posted - 11/15/2010 :  01:36:22  Show Profile  Reply with Quote
you are correct Mr.gail
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000