Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 437
  • Last Modified:

Best config for Sql 2008 x64 on Windows 2003 x64

I need some help building out this system.
I built it out with two 8 drive ADG Logical drives.
I put Data on one logical drive and OS,Logs,Backup on the other.
It was my understanding that ADG would be faster than Raid 10, regardless I didn't have enough drive space to do raid 10 at the time.
I plan to move an existing MSA 500 with 14 146 gig 15K drives to this machine, with a dedicated controller (the one that comes with the msa500.
Is it best to create a new ADG Logical drive or a raid 10 drive.  What should I put on that drive (data or logs or both?
Should I Reconfig the non OS partition back to raid 10?
BTW, all the sas drives are DP.
Both P400's have 512 BBWC
The MSA 500 has 512 BBWC
My perfmon shows low use of the current data logical drive, but high use of the log logical drive.
  • 3
  • 2
1 Solution
superbrianAuthor Commented:
The drives in the MSA 500 are U320 drives.
Yes, this server really has 6 cores x 4 processor.  I called HP for support and they guy said they didn't make such a thing.  It' brand new.
In your case I would put the

OS on a RAID 1 (2 drive set) separate from the database.
Make a RAID 10 Logical for DATA
Make another RAID 10 Set for Logs with lower stripe sizes.

Take the OS storage and Swap out from your DB storage.

superbrianAuthor Commented:
I can't afford the down time to rebuild the OS so Array 0 can't be changed.

Array 1 can be changed since I can be down long enougth to move data/logs around.

Array 2 will be the new 14 Drive U320 Array.

Array 0 - 8 drive ADG SAS has:
C:   OS
D:   SQL
E:   Backups
J:   Logs
I was planning to conbine E: and J: as a new larger E: for just backups.

Array 1  - 8 Drive ADG SAS has:
F:   Data
G:   Data
H:   just some extra space

Array 2 will be a new 14 Drive U320 array on the MSA 500  
Should this be ADG or Raid 10  Which will offer the most safety and speed.
Should I put logs or data on the new Array 2?
It will be a waste of space to use it for logs, but that would seem to offer the best performance.
I would strongly recommend you analyze where the disk-slices (partitions) on the Logical Volume 0 are.

Closer each partition is to the center of each disk spindle the more performance you'll receive on spin speed alone.

Here are some assumptions on my part.

C:  - Server OS and Its Swap File
D:  - SQL Server Binaries etc
E:  - SQL Server Maintanace Plan \Backups directory container.
J:  -  SQL Server transaction Logs

J: is all the way at the end of the Logical Volume so has the _SLOWEST_ spindle speed,

My first recommendation  would recommend swapping J: and E: volumes places (unless the partitions are issued differently.

F: SQL Server \DATA containers with the real tables in them.
G: SQL Server \DATA containers with the real tables in them.
H: Lef over Space

Okay So on the Same IO Backplane

C:\ is going to get alot of SWAP hits and fragmentation as you update packages via Windows Installer.

D:\ SQL Server Binaries could have stayed on C: (You can still migrate that) rapid access to binaries is not needed.  It's only used during SQL Start/Stop upgrades etc..

E:\ Should be your Logs

J:\ Should be your backups

F and G can merge together (slice 0 and slice 1)

Now database files grow in strides just like logs, you need set the DB growth from the beginning and make sure each start at the begining of the volume.

Your DB logs should be closest to the centre spindle slices.  Either on array 1 or array 2
Your High I/O database (not the one thats caching alot, but actually doing alot of INSERTS, DELETES and UPDATES) that Data needs to sit on ARRAY 2 (No need for separate slices)

This is the best that I can give you without knowing the sizing requirements for the afore mentioned database(s) and how many reads, writes, in-memory stored procs and etc will execute on it.

I would always stick with RAID 10 vs. ADG
And pay attention closely to block sizes when formatting NTFS etc..
Default size is not always best for I/O chunks.

superbrianAuthor Commented:
Thanks DJDecay, that helps me understand a lot, and I'll make most of those changes.
I'll create array 2 as Raid 10 and recreate array 1 as Raid 10 and I'll put logs and data first on each.

My main database is 35 gigs, whats the recommended block size?  I usually leave this at default since I don't know what's best.  It seems to me it should be quite large if the data is 35 gigs and I want to place it on the new array 2.  The other 10 DB's are 1-4 gigs each

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now