durai nagarajan (1/13/2013)
Jeff Moden (1/13/2013)
There are some mitigating factors such as whether or not the database has been changed to bulk or simple recovery modes but, if no such thing has happened, nightly full backups and hourly log backups will all point and time recovery to virtually any time after the earliest full backup that you have. Recovering to a time after the last scheduled log backup is also possible if the system will allow you to do a "Tail Log Backup" prior to beginning a restore.
thanks jeff, i understand what you are saying but just thought of asking whether any work around is available because in case i need a database in a state it was before 5 week i need to take my VP approval to get the DB from tapes.
No. Like Gail and Lynn have stated, you can only go as far back as the last full backup that you have. Log restores are only "roll forward" and cannot be used to "roll back".
It's actually good that you would need to get VP approval to go back earlier than that. That means that something has gone seriously wrong and, since the VP didn't tell you to do it, it means the VP doesn't know that something desparate needs to be done. Don't look at it as a hurdle. Look at it as a safeguard that's gonna cover your butt in the long run.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs