locked
Content Data Bases going to incorrect drive RRS feed

  • Question

  • Our SQL database is set to default to putting new DBs on the G drive and SharePoint is putting them on H. Why is SharePoint creating these DBs on H? I can't find anywhere in SharePoint to change the default drive, but it is obviously ignoring SQL's default settings.
    Monday, May 16, 2011 8:01 PM

Answers

  • Hi Lalewicz,

    Based on my research, SharePoint uses a very simple Transaction SQL(T-SQL) to create the content database while creating a web application. The T-SQL statement is like:

     

    CREATE DATABASE [The name of ContentDatabase] COLLATE [Server collation]
    

     

    As you can see, there is no path parameter applied to the CREATE DATABASE command.

    Back to your questions, could you please verify again that the "Database default locations" is corrent(means it is H) in your database server.
    If you are using named instance SQL Server, please make sure you are connecting to the correct instance.

    For more information about how to change the default location, please see:
    http://blogs.technet.com/b/sharepointcomic/archive/2008/09/19/change-default-location-for-sharepoint-database-files-mdf-ldf.aspx

    If there is anything unclear, please feel free to ask.

    Thanks,
    Jinchun Chen


    Jin Chen - MSFT
    Thursday, May 19, 2011 1:44 AM
    Moderator