![]() Of course, if you did not anticipate the damaging event, or you do not use database snapshots as part of your regular data protection strategy this may not be an option for you, and you will be forced to use the point-in-time restore method. If you know that you are going to perform a task which may damage your data, it would be prudent to take a database snapshot before you do it.ĭatabase snapshots are quick and easy to create, and very easy to roll back. ![]() SQL Server provides two mechanisms for you to recover from these events: Your attempted database upgrade failed, and left the database in an unknown state.Someone executed an update without a WHERE clause.There may be various reasons why this could be necessary but it is usually related to the execution of accidental or malicious DML or DDL statements. There are certain circumstances in which you may need to roll back your database to a specific point in time.
0 Comments
Leave a Reply. |