3 Replies Latest reply: Jan 9, 2013 5:10 AM by radek.kubka RSS

SQL Server Best Practices Architecture UCS and FAS3270

MPITTSER1
Currently Being Moderated

Hey there

 

We are moving from EMC SAN and physical servers to NetApp fas3270 and virtual environment on Cisco UCS B200 M3.

 

Traditionally - Best Practices for SQL Server Datbases are to separate the following files on spearate LUN's and/or Volumes

 

  • Database Data files
  • Transaction Log files
  • TempDB Data files

 

Also I have seen additional separations for...

  • System Data files (Master, Model, MSDB, Distribution, Resource DB etc...)
  • Indexes

 

Depending on the size of the database and I/O requirements you can add multiple files for databases.  The goal is provide optimal performance.  The method of choice is to separate Reads & Writes, (Random and Sequential activities)

 

If you have 30 Disks, is it better to separate them?  Or is better to leave the files in one continous pool? 

 

  • 12 Drives RAID 10 (Data files)
  • 10 Drives RAID 10 (Log files)
  • 8 Drives RAID 10 (TempDB)

 

Please don't get too caught up on the numbers used in the example, but place focus on whether or not (using FAS3270) it is better practice to spearate or consolidate drives/volumes for SQL Server Databases

 

Thanks!

More Like This

  • Retrieving data ...