As a database grows and performance and maintenance demands increase, the
usage of filegroups becomes a necessity. New features within SQL Server 2005 leverage
filegroups; some focus on performance, and some improve filegroup involvement in disaster
recovery.
Even though the functionality has been available for years, few environments use
specific filegroups either for performance or backup optimization. Whether a database
is 1GB or 1TB, it??™s often with a single filegroup. True, databases often have multiple files,
which can present some performance gain, but the benefits of a well-designed filegroup
implementation can make the difference between a scalable system and a nonscalable
system, both in terms of performance and recoverability.
While it??™s obvious that filegroups make sense for a 1TB database, it may seem that
maintaining a filegroup scheme for a 1GB database creates more administrative work for
very little gain. Filegroups do introduce additional administration, but they can provide
surprising results, even for a relatively small database. For full-text search, SQL Server
2005 introduces new functionality that incorporates the backup of an external full-text
catalog with the backup of a specific filegroup.
Pages:
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174