SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Placement of SQL Server Data and TLog files in a SAN Infrastructure and Monolith Storage Environment...


Placement of SQL Server Data and TLog files in a SAN Infrastructure and Monolith Storage Environment

Author
Message
humbleDBA
humbleDBA
SSC Eights!
SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)SSC Eights! (852 reputation)

Group: General Forum Members
Points: 852 Visits: 1508
Andy sql (4/15/2014)
There is no way that a single SQLIO exe, running on a single server, should be able to bring down your SAN!

If you know that you are not allowed to run a stress-test tool, then an alternative is to simply copy a large MDF file between partitions, and measure how long it takes. Not exactly scientific, but is a real-world situation.


To Stress test a SAN's storage you have to run against the LUNs presented and to ensure you saturate the SANs cache, and doing that - as I have done a few years back when I had such a chance to test the SAN infrastructure before going into production - will stress the SAN and will dramatically slow it down, causing problems for applications. If you don't do this, then the figures are useless in telling you at what load the IO subsystem can handle.

I also know it is possible to bring a SAN to its knees because on another gig I did, where I was brought in to help with a SQL Server performance issue for a well known high-volume internet sales site, the incumbent DBA had brought their systems down when he carried out a 'stress-test' using SQLIO without telling anyone he was doing the work.

Sorry, but no apology for my comments here.
Thanks anyway

Edit: I've added links here that are helpful to the points I raise...

http://technet.microsoft.com/en-us/library/cc966412.aspx
http://technet.microsoft.com/en-us/library/ms187104(v=sql.105).aspx
http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/05/25/parsing-sqlio-output-to-excel-charts-using-regex-in-powershell.aspx
http://www.brentozar.com/archive/2008/09/finding-your-san-bottlenecks-with-sqlio/
http://blogs.technet.com/b/josebda/archive/2013/03/28/sqlio-powershell-and-storage-performance-measuring-iops-throughput-and-latency-for-both-local-disks-and-smb-file-shares.aspx
http://www.sqlteam.com/article/benchmarking-disk-io-performance-size-matters
http://blogs.technet.com/b/sqlpfeil/archive/2012/12/04/working-with-sqlio-and-analyzing-it-s-output.aspx
http://blogs.msdn.com/b/sqlmeditation/archive/2013/04/04/choosing-what-sqlio-tests-to-run-and-automating-sqlio-testing-somewhat.aspx
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/a7ce8a90-22fc-456d-9f56-4956c42a78b0/sqlio-block-size-iossec
Jo Pattyn
Jo Pattyn
SSCertifiable
SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)

Group: General Forum Members
Points: 7135 Visits: 10009
(1) how important, performance-wise, is it to separate out these files?
->it is easier for management in case you decide to reorganize storage. Logfiles have mostly sequential reads, datafiles are mostly random io. Logfiles could be moved later to fast sequential disks (smaller capacity but more) and some datafiles to flash-storage (great reads)
(2) is there a benefit in having the data and tlog files on separate windows volumes (ie, storage-based LUNs), based on the fact that all the data is spread across the whole of the storage array anyway?
->Same as above, allows for easier storage tiering/isolation/monitoring/redirection when seperate
(3) will having separate volumes (ie, storage-based LUNs) mean that there will be separate paths for the data to travel to and from the storage array through the SAN fabric, will this help with performance, and if yes, how?
->It probably generates seperate paths, depends on the storage/fabric if there is some quality of service. There can be paths with high priority (like fast fabric) and with lower priority (slower fabric in case fast gets overloaded).
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search