Not having an encryption key to restore could be unpleasant
in that scenario.
ReportServerTempDB
There??™s really no direct need to back up ReportServerTempDB, since it is intended to be
a temporary database. However, if you??™ve implemented some of the advanced report
caching features with Reporting Services and have a fairly large deployment (more than
100 reports or more than 1,000 users), there could be a significant performance impact if
ReportServerTempDB is effectively reset. There is an advantage to keeping a backup
ready to return the Report Server to optimal performance as quickly as possible.
CHAPTER 3 n RESTORING A DATABASE 70
Databases in SUSPECT Status
Nothing instills more panic for a DBA than seeing a database in SUSPECT status. A database
is placed in this status if SQL Server attempts but is unable to bring the database
online, whether in ONLINE, SINGLE_USER, or RESTRICTED_USER mode. The SUSPECT status can
be caused by one the following scenarios:
??? One or more required data files are missing.
??? One or more required data files are damaged.
??? Recovery is not possible due to missing log files.
Pages:
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167