For example, when partitioning an order table, you could create
a separate filegroup for each sales region and create a scheme to route data to the
appropriate area. If well designed, the performance results will be impressive. Simply
testing this feature with multiple USB drives acting as filegroups showed a visible
impact on my humble laptop computer.
Isolating Specific Tables
You may need to protect specific tables or isolate seldom updated data. In SQL Server
6.5, you could back up and restore individual tables; when 7.0 came out, that feature
was removed (probably because PSS was inundated with calls about databases going
into SUSPECT status after a single table??”transactionally inconsistent??”was restored). The
only way to back up specific tables post-SQL Server 6.5 is to place them on a separate
filegroup to be backed up independently of a full backup.
You also may want to isolate specific tables for backup/restore purposes. This could
be to move tables that rarely need to be backed up on separate filegroups, or to move
tables that change often. As you??™ll see shortly, having a separate filegroup to handle a
full-text index backup is a must.
Pages:
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189