SAN Connected Environment ans System databases

  • Hi all - my question is simple really.

    In a SAN attached SQL Server which has sepearate LUNS for the Data, Log files and TempDB where would you place the system databases.

    At present I thinking best practice is to put the TempDB mdf and ldf on its on LUN. The Master, Model and MSDB mdfs on the data LUN and the Master, Model and MASB ldf on the transaction log LUN.

    Comments appreciated

  • probably over kill , but it will work.

    tempdb on it own fast LUN is a must.

    model, master and msdb can go together but there is no real need to seperate the mdf and ldf. model is the only DB that is in FULL recovery mode by default.... and it is not changed often.

  • I would agree with Geoff. The master/model/msdb databases shouldn't see a lot of activity, so they don't need to be separate. The tempdb will, so having a separate LUN for that can really improve performance.

    I would be aware that if you move the system dbs to the SAN and for some reason look to attach these LUNs to another system, that SQL Server might not start unless you have the drive mapping for the LUNs the same. SQL stores pathing inside master.

  • Ok so I will be fine leaving master\model\msdb on the local drive rather than the SAN, and I will move tempdb to its own LUN?

    Obviously the User databases will use the Data and Transaction Log LUNS created.

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

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