When they were created, I??™m sure someone decided that there would never be more than
50MB of data stored. As a result, these evolving database designs, both logical and physical, usually
aren??™t built for any sort of scalability. I get involved because the performance of that 20GB database
becomes unbearably slow.
When I have the luxury of working on a project from day one, I always stress planning for
extremes. You say you currently have only 50 users? Plan for 50,000. You don??™t think that using filegroups
will be necessary for either performance or recoverability enhancement? Build them anyway.
I??™ve never seen an operational database (that is, a database other than a data warehouse or other decision
support database) that hasn??™t grown and evolved both in volume and functionality.
Using filegroups is a simple way to plan for extremes. Get in the habit of always specifying a filegroup
when creating objects, even if you aren??™t using multiple filegroups. When the day arrives that you
do, you??™ll save yourself from numerous headaches. If you aren??™t in the habit of explicitly specifying a
filegroup, it can be easy to place objects where you don??™t want to.
Pages:
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183