Should I configure the second sql instance to use same C:\ drive root directory path as the exiting Default instance?

  • What are the guidelines for the the root directory path for a second sql server instance being added to the same server where a 'default' instance already exists with its root directory on the same C: drive?

    What will happen if I, instead, use the E: drive for the root directory for the second instance?

  • The instance will function just fine.

    I like to move my default path off of C in the first place. I also like to have a different path for each instance.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • It does not matter where you let the SQL executable reside.

    I never, ever use Drive C for anything. Not even the OS. I install all other instances on the same drive as the Default and then place the actual data files on the drives with the default instance system databases, but into their own respective directory.

    I use one spindle for the executables, one spindle for the Data Files, one Spindle for the Log Files and one spindle for the Temp Database. For any really large database, or database that has high transactions, I place that one on its own spindle as well.

    Andrew SQLDBA

  • But aren't there some 'shared' files/folders/etc. that will need to be updated (or written to) on the default instance's root directory when the second instance is installed?

    So what happens to these shared files/folder/etc. if that second instance is installed on another drive?

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

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