Manually recreating the User Profile Services application does not use the preconfigured database prefix in the AutoSPInstaller XML.
[xml]$xmlinput = (Get-Content "\\sp01\SharePointInstall\AutoSPInstaller\AutoSPInstallerInput.xml") -replace ("localhost", $env:COMPUTERNAME)
. \\sp01\SharePointInstall\AutoSPInstaller\AutoSPInstallerFunctions.ps1
CreateUserProfileServiceApplication([xml]$xmlinput)
This creates three databases on SQL Server with the following names: Profile, Sync, Social
The configured databases prefix in our XML:
Database prefix:
<DBPrefix>SPDB</DBPrefix>
So I would expect SPSB_Social, SPDB_Sync and SPDB_Social.
Unfortunately renaming the databases is not possible so I had to recreate the service application.
Comments: ** Comment from web user: brianlala **
[xml]$xmlinput = (Get-Content "\\sp01\SharePointInstall\AutoSPInstaller\AutoSPInstallerInput.xml") -replace ("localhost", $env:COMPUTERNAME)
. \\sp01\SharePointInstall\AutoSPInstaller\AutoSPInstallerFunctions.ps1
CreateUserProfileServiceApplication([xml]$xmlinput)
This creates three databases on SQL Server with the following names: Profile, Sync, Social
The configured databases prefix in our XML:
Database prefix:
<DBPrefix>SPDB</DBPrefix>
So I would expect SPSB_Social, SPDB_Sync and SPDB_Social.
Unfortunately renaming the databases is not possible so I had to recreate the service application.
Comments: ** Comment from web user: brianlala **
Confirmed. I will update the script to make sure that each function (such as the User Profile Service App) defines the $dbPrefix variable explicitly within it instead of assuming it's already been defined (which it of course wouldn't be yet if we are running individual functions in isolation).
This will be fixed in the next release (shortly).
Brian