Primary Filegroup for System Objects on a SAN

  • Hello,
    I'm either looking for clarification or redirection.
    I'm commissioning a new database that will eventually grow into a very large OLTP database.
    Traditionally I've always separated the physical disks that Data and Log files are on and used a separate Filegroup for non system objects and data.
    My new system is going to be on a SAN and although they have allocated separate drives for me they are all on the same LUN.
    So is there any reason to separate the non system objects and data out of the Primary Filegroup?
    Out of intererest I'm also pushing for a separate drive for the TempDB too, so we can size it to fill the drive, if you'd like to comment on that too?
    Thanks
    Giles

  • giles.clapham - Monday, August 14, 2017 8:26 AM

    So is there any reason to separate the non system objects and data out of the Primary Filegroup?

    Same reason as you'd separate system and non-system objects on any storage - fast restores, ability to do partial restores to get the DB up and running faster after a disaster.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 2 posts - 1 through 1 (of 1 total)

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