UNSOLVED

Satrum

updated

7 years ago

S

Satrum

5 Posts

0

1401

January 26th, 2020 05:00

Unity 550F SQL - Thick or Thin provisioned LUNs

Hi

I'm currently configuring a new Clustered SQL server on a Unity 550F.
This will be a highly IO intensive SQL cluster so I just want to confirm what is the latest recommendation regarding Thick/Thin LUNs on the Unity.

According to the following article:
https://community.emc.com/docs/DOC-66169
1)  There are future features being planned for the Unity Operating Environment that cannot be utilized by Thick DLU LUNs, such as In-Line Compression (ILC).   
    2)  Although traditional Thick LUNs may provide higher performance characteristics in some situations, there are future Flash drive and Meta-data caching features being built into the Unity Operating Environment that are expected to eliminate most, if not all, differences in performance between Thin LUNs vs. Thick LUNs.

Does this hold true for Unity 550F, Code: 4.5.1.0.5.001

Thank you!

  • DELL-Sam L

    Community Manager

    8058 Posts

    34386 Points

    1209

    0

    Posted January 27th, 2020 10:00

    Hello Satrum,

    Here is the link to Dell EMC Unity: Microsoft SQL Server Best Practices guide.

    https://dell.to/2Gv6Hpz

    Please let us know if you have any other questions.

  • Satrum

    5 Posts

    1204

    0

    Posted January 27th, 2020 17:00

    Hi Sam

    Thanks a lot for your reply!
    I've read through the documents and moving forward with block over FC is already decided.
    My question was more in regards to the differences between Thick and Thin LUNs at this stage using an All-Flash array.
    If there's close to no performance impact using Thin LUNs - I would prefer it.
    If there are still some noticeable gaps in performance between Thin and Thick LUNs - I may need to go with Thick LUNs for this cluster.

    Hope that makes sense!

    Thank you!

  • DELL_ChrisHolloway

    2 Intern

    125 Posts

    1200

    0

    Posted January 28th, 2020 01:00

    Do you plan on using snapshots/thin clones, async replication, or data reduction?  In which case go with thin.

    You might find thick is better performance is your application uses a sequential workload.  But really the best way to tell is for you benchmark both LUN types with your application, or a workload generator like vdbench that mimics your workload.

    In my experience, most people use thin LUNs.