tonzur40
asked on
Sql Server disk configuration
I have a SQL server that is used for both write and read. I have a host with 8 15K drives and I need to configure the SQL server and the Databases. I have thought of 3 scenarios
Raid 1 for OS, Raid 10 (4disk) for my Data file and Raid 1 logs file
Raid 1 for OS, Raid 10 (6disk) for my Data file and logs file
Raid 10 (8disks) for everything
Any other ideas?
Raid 1 for OS, Raid 10 (4disk) for my Data file and Raid 1 logs file
Raid 1 for OS, Raid 10 (6disk) for my Data file and logs file
Raid 10 (8disks) for everything
Any other ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Go with John Tsioumpris setup suggestion.
I'd likely put the OS + Logs on one disk, as once your OS starts up + loads the OS into memory, your OS disk access should be minimal... well... depending on if you have enough memory to keep from swapping... and have no other disk hog applications running that produce massive i/o thrash on the OS disk.
I'd likely put the OS + Logs on one disk, as once your OS starts up + loads the OS into memory, your OS disk access should be minimal... well... depending on if you have enough memory to keep from swapping... and have no other disk hog applications running that produce massive i/o thrash on the OS disk.
Information missing to say for sure, size of available drives,
Server specs.
The log files are potentially high I/o placing them in the same spindles as the os where commonly the page file is, when the resources are need for swap, the decline in performance could be in geometric proportions.
Size of databases involved, transaction log sizes can be managed by SQL jobs for transaction log backups on a frequency.
Echo your first indicated option.
Server specs.
The log files are potentially high I/o placing them in the same spindles as the os where commonly the page file is, when the resources are need for swap, the decline in performance could be in geometric proportions.
Size of databases involved, transaction log sizes can be managed by SQL jobs for transaction log backups on a frequency.
Echo your first indicated option.
ASKER
Thanks a lot I will go with option 1
Please take this with a spoonful of salt.