If you
restore the database with the REPLACE option, the transaction log will reset and those tail
transactions will be lost.
SQL Server 2005 now prevents you from restoring a database without first backing up
the log??™s tail. If you attempt such a restore, you??™ll receive the error shown in Figure 3-5.
CHAPTER 3 n RESTORING A DATABASE 55
Figure 3-5. SQL Server 2000 and earlier offered no warning that the tail of the transaction
log would be overwritten. This is a nice addition.
This addition of a simple error message should eliminate a common and costly mistake.
While the error message suggests using WITH REPLACE or WITH STOPAT to bypass this
error and proceed with the recovery, do not do so.Make it a habit to back up the tail of
the transaction log every time you perform a restore. Using a different procedure to
bypass the log??™s tail should clearly be an exception to the process.
nNote Replacing a database snapshot (discussed at length in Chapter 9) doesn??™t result in a prompt to
back up the log??™s tail.
Restoring in Bulk-Logged Recovery Mode
When in Bulk-Logged Recovery mode, you can only restore to a point in time up to the
most recent bulk-logged action.
Pages:
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144