This project has moved and is read-only. For the latest updates, please go here.

Central Admin not creating DB with Prefix

Apr 24, 2012 at 7:16 PM
Edited Apr 24, 2012 at 7:16 PM


I have done successful implementation sofar with AutoSPInstaller, want to check to see if Central Admin along with all other DB's created, can be created with Prefix without GUID.

Ex: it currently shows  WSS_Content _(GUID),  can we have it automatically created with prefix (SH_Test_CentralAdmin) ?



Apr 25, 2012 at 9:09 AM
Edited Apr 25, 2012 at 9:12 AM

Hi Ramii,

check the database settings part in your xml file, based on your input it should look somewhat like this:

<CentralAdmin Provision="localhost">
  <!-- If you are creating an alias (recommended!), <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance. 
  If you leave <DBServer> blank or specify localhost, script will assume the local server for SQL databases -->
  <!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
  <DBAlias Create="true"
    DBPort="1433" />
  <!-- The DBPrefix is prepended to all database names. e.g. If you set this to TEST, your config DB will be TEST_ConfigDB.
  If you set the prefix to localhost, script will prepend each database with the name of the server on which the script is run. 
  Leave this blank for no prefix.
  NOTE: If you are installing a multi-server farm, it is recommended that you do not use localhost as services provisioned on different servers
  will have different prefixes.
  <!-- The name of the farm configuration database -->

This will create your databases like this:
Configuration Database: SH_Test_ConfigurationDBName
Central Admin Content Databse: SH_Test_CentralAdmin

Best Regards,

Apr 25, 2012 at 12:59 PM
Edited Apr 25, 2012 at 1:23 PM

Let AutoSPInstaller do all the work and it will take care of the CA Creation. Some tries  to run the config wizard to create the farm then use AutoSPInstaller to complete the config, this would result in the GUID Suffix for the CA Content Database.

Also CA Database standard naming convention is SharePoint_AdminContent_(GUID) if you run Config wizard and Prefix_AdminContentDB if you run AutoSPInstaller

WSS_Content is the standard naming prefix for Content Databases.

Apr 25, 2012 at 9:16 PM

Hi Thanks for your quick replies,

I have used similar script and I got config DB created with  SH_Test_ConfigDB,

 but for the  Central Admin Content DB, it got created with WSS_Content _(GUID).