I was wondering if anyone played around with changing the allocation unit size when formatting the hard drive the SQL server is running on. I would think that setting it higher to account for the larger size of the database files would help, but I'm not sure.
Anyone have any thoughts?First, make sure you have a good backup and can restore from it. Stop the service before formatting. Make sure the backup is on another machine or drive.|||While you might be able to find better drive geometry parameters, I've never seen a case where that happened. Windows 2000 and later has never yet failed to pick the best geometry for me.
-PatP|||I have never played with the allocation size in Windows 2000. Theoretically, you might (stress that word, please) get a small benefit from going to an 8Kb allocation size. Then you might be able to turn off the Torn Page Detection on your database. All very theoretical, and unproven. It would probably be better to just use raw devices, instead, but you will increase your administration costs, if you do that. Enough that you would only want to do this for really mission critical stuff, and you had already proved that it gave a significant boost to performance. And by "significant", I mean enough to offset the increased admin costs.sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment