In particular, the impact of having a backup of the PRIMARY filegroup is
critical. Take special care on the following points:
??? Make sure you set the default filegroup: If you use multiple filegroups, don??™t leave
the PRIMARY filegroup as the default. The PRIMARY filegroup has to hold the .mdf file,
which has metadata about the database structure. It??™s best to separate that from
actual user data.
??? Transaction logs are your life: This can??™t be said enough. To restore individual files
or filegroups, a full transaction history is necessary.
??? Get in the habit of specifying the filegroup before creating the table: Never create a
table or index without the ON <
> clause, even if you only have one
filegroup (which, of course, would be PRIMARY). One of the keys to avoiding the mistake
of placing objects on the wrong filegroup is to get yourself in the habit of using
that ON clause. Trust me, it helps.
??? Be aware of a full-text backup: Whether you want the full-text catalogs backed up
or not, be aware of how a full-text backup works in SQL Server 2005.
Pages:
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207