Storage Design for VLDB

  • We are in process of migrating from 1 DC to another. We have one SQL instance per server and large databases hosted per instance where the largest being ~2TB. Below is our current disk configuration:
    Data: 5.5TB
    Log: 800GB
    TempDB: 400GB
    Our new DC storage admin says that they generally do not create LUNS larger than 500GB for SQL Data (or 1TB at the worst) and suggests to create 'n' volume mount points each with 1 LUN for SQL data. This also means we would need to have multiple data files spread across the 'n' data mountpoints. He says that 500GB LUN limit for SQL Data is as recommended by Microsoft for troubleshooting performance problems. 
     I would like to know can be an optimal storage design and does his claim of MS recommended size for SQL Data is correct ? I tried searching online but could not find anything as such, hence wanted to take others opinions.

    Thanks

  • It depends: https://www.brentozar.com/sql/sql-server-san-best-practices/

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • harikumar.mindi - Monday, February 19, 2018 5:22 AM

    We are in process of migrating from 1 DC to another. We have one SQL instance per server and large databases hosted per instance where the largest being ~2TB. Below is our current disk configuration:
    Data: 5.5TB
    Log: 800GB
    TempDB: 400GB
    Our new DC storage admin says that they generally do not create LUNS larger than 500GB for SQL Data (or 1TB at the worst) and suggests to create 'n' volume mount points each with 1 LUN for SQL data. This also means we would need to have multiple data files spread across the 'n' data mountpoints. He says that 500GB LUN limit for SQL Data is as recommended by Microsoft for troubleshooting performance problems. 
     I would like to know can be an optimal storage design and does his claim of MS recommended size for SQL Data is correct ? I tried searching online but could not find anything as such, hence wanted to take others opinions.

    Thanks

    Tell him you are interesting in learning more about MS recommendations and ask if he can provide the link to this information.
    People will say whatever along with "Microsoft recommends...". And often Microsoft really does not. Just because someone says so, doesn't make it true.
    If you do get a link, please post it. I'd be interested in reading it.

    Sue

  • @alzdba - Thanks for the link. I searched on Brent's website but somehow missed this link 🙂 Will go through that and try to get more info.
    @sue - "People will say whatever along with "Microsoft recommends..." That is most of the time true. I am really not sure  about why they are so hesitant about bigger LUN's.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply