May 20, 2013 at 3:51 am
Hi All,
I am in the process of putting together a proposal to upgrade our Production Server and wanted to ask a couple of questions of the experts on this site.
Basic Specification is ;
Windows Server 2008 OS
SQL 2008 R2 - Single Default Instance
ERP System with 6 Databases of around 6 gig each ( 36 gig total ... this is 4 years of data )
Daily / Hourly tasks running
Full Backup @ 2am
T-Log backup every 2 hours from 6am - 10pm
Processor - is a given that it will be high spec
Memory - 16gb or 32gb
I am looking at the following for storage;
PARTITION 1 - RAID 1 - OS ( 2 Drives 300gb each ) or 500gb depends at time of purchase
PARTITION 2 - RAID 1 - SQL Databases and Indexes ( 2 Drives 1 tB each )
PARTITION 3 - RAID 1 - SQL Logfiles ( 2 Drives 1 tB each )
PARTITION 4 - RAID 1 - TempDB ( 2 Drives 1 tB each )
PARTITION 5 - RAID 5 - Backups and software storage/updates ( 3 Drives 1 tB each )
Thoughts and suggestions on configuration please
________________________________________________________________________________________________
Regards
Steve
SQL 2008 DBA/DBD - MCTS/MCITP
Please don't trust me, test the solutions I give you before using them.
May 20, 2013 at 4:34 am
That's a very low number of drives for each RAID array. Low usage DB I presume, since they are pretty small...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 20, 2013 at 7:02 am
Hi Gail,
Thats why I am asking for suggestions - the book said to set up the Raid 1 and Raid 5 for Backups - but not about sizing or number of drives.
The space is correctly identified - so could have 4 500gb drives on Raid 1 possibly ?!
Thanks
Steve
________________________________________________________________________________________________
Regards
Steve
SQL 2008 DBA/DBD - MCTS/MCITP
Please don't trust me, test the solutions I give you before using them.
May 20, 2013 at 7:22 am
I hope the book didn't say RAID 0, because that's something you never want to use for a database.
IO throughput is a function of the number of spindles you have in an array, the more spindles, the higher the data transfer rate.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 20, 2013 at 7:39 am
definetly not RAID 0
________________________________________________________________________________________________
Regards
Steve
SQL 2008 DBA/DBD - MCTS/MCITP
Please don't trust me, test the solutions I give you before using them.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply