Figure 3-10. The resource database is a system database, but you won??™t see it in SQL Server
Management Studio. That doesn??™t mean you shouldn??™t back it up, though.
However, if you look on the file system, you??™ll see two files: mssqlsystemresource.mdf
and mssqlsystemresource.ldf, as shown in Figure 3-11. These two files represent your
resource database. Unlike with other databases that are exclusively locked when the
instance is running, you can copy and paste both of these files to a new location.
Figure 3-11. The resource database files appear as normal database files, with both a data
file (.mdf) and a log file (.ldf).
CHAPTER 3 n RESTORING A DATABASE 69
Backing up the resource database is critical because SQL Server won??™t start without
it present and in the same location as the master database. Unlike other databases, you
can??™t back up the resource database with T-SQL commands; you must simply copy and
paste the resource database to another file location, then back up those files to tape.
Even though resource is locked while SQL Server is running, you can still copy and paste
the open files without fear of data corruption.
Pages:
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165