Quantcast
Channel: Forum Getting started with SQL Server
Viewing all articles
Browse latest Browse all 7129

performance optimization of IaaS SQL 2016 using separate P30 azure drives versus using storage spaces virtual disk with simple option (raid 0, stripe only)

$
0
0

We want performance optimization of IaaS SQL 2016 using separate P30 azure drives versus using storage spaces virtual disk with simple option (raid 0, stripe only).  

Azure P30 has 200 mb/sec throughput and 5000 IOPs which can be pooled into a storage pool then configured with a virtual disk with simple mode (stripe with no parity ).  Note we are not choosing mirroring or parity options.   

Would it be better to create three dedicated drives for temp, log, and databases?  We can also control caching so that temp drive has a read/write cache, log drive has no cache, and database drive is read only cache.   Each dedicated drive will be a P30 drive.   We used a Microsoft provided template from the Azure Microsoft store which deployed a SQL 2016 enterprise with a 1 TB (P30)  F drive.  This drive came with a temp database and a temp log file already on this drive.  In this dedicated drive scenario what size disks would you attach (larger disk would have more IOPs and throughput). P30 has 5000 IOPs and 200 MB/sec throughput.

If we created a storage space using another P30 disk and the pre-created  F drive which has a live temp db and temp log would we damage the temp files?  And if we decided to add a 3rd P30 drive to a working 2 disk P30 storage pool/virtual disk ( simple- stripe only) could this damage the database files? 

Which option would provide better performance or is this just overkill?  I am noticing the (Simple) stripe recommendation using storage spaces in the below link.  I thought Simple which is like a Raid 0 is vulnerable to failure?  If we have a two disk in Simple mode (stripe only, no parity) will losing one of the disk cause a failure to the virtual disk?

Database server: 3xP30 (striped).     Very reluctant to use storage spaces because it is my understanding as a software based RAID they are slower than a hardware based RAID.  And the below SCCM Azure recommendations is recommending stripe with no parity or mirroring?  Adding parity or mirroring would slow down the disks hence they must be referring to Simple (stripe only).  Please confirm that they are talking about Simple mode in the below link?

https://docs.microsoft.com/en-us/sccm/core/understand/configuration-manager-on-azure


dsk




Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>