PRIMARY is a perfect example, because it
exists in each database. I highly recommend naming each filegroup uniquely throughout
an entire instance, particularly when working with a high number of databases on a single
instance.
CHAPTER 4 n BACKING UP AND RESTORING FILES AND FILEGROUPS 79
The Default Filegroup
If you don??™t specify any filegroup when creating an object, it will be placed on a default
filegroup. Initially, this default filegroup will be the PRIMARY filegroup, but I highly recommend
adding at least one additional filegroup and specifying it as the default. The
PRIMARY filegroup will always hold the .mdf file and thus all of the system tables for the
database. By creating a second filegroup before creating objects, you can separate the
technical information for the database from the actual user data. That second filegroup is
a better candidate for being the default group. Mixing actual, active data (meaning it is
constantly updated) with the metadata contained in the .mdf file is a recipe for disaster.
SQL Server can have only one default filegroup per database.
Pages:
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179