April 27, 2007 at 12:26 am
This isn't exactly performance 'tuning', but it is performance related. If it belongs somewhere else, feel free to point that out too.
I've been asked to spec up a server that is going to be used for reporting only and was wondering if I've gotten anything wrong with my thinking.
Is there any need to put anything other than the data files on their own arrays? ie.
Array1. OS/swap file
Array2. logs (alls dbs)
Array3. Data file
Array4. Data file (if more than one db on server)
Any thoughts?
April 30, 2007 at 10:44 am
as with all things it depends upon what the load will be!
Usually a reporting server is high in reads which means you might be able to use raid 5, however I bet you'll do some heavy data loads in which case tlogs will be important, even in simple mode as the data still has to write.
page file should do nothing on a dedicated sql server, but if in doubt place it on your fastest array and peg the size to a fixed amount.
Tempdb may be hit heavily so you might want tempdb on its own array, make sure this array has the same number of spindles as your data drive otherwise you introduce a bottleneck, consider creating multiple files, 1 per core and enabling the trace glag to make sure it works!
I always go for as much memory and spindles as I can get - your question is really far too general to make a serious recommendation.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply