Do the following:
- Configure Apex Central to use a different database.
This includes the following:
- Using the same database, but on a different SQL server
- Using a different database on the same SQL server
- Using a different database on a different SQL server
- If you are moving the Apex Central database to another SQL server, then follow the steps in this article:
Moving databases between computers that are running SQL Server
- Set an account to be part of the DBO scheme for the Apex Central database.
It is possible that while moving to another server, the account associated with DBO is no longer available.
Make sure to set the following permissions:
- Mixed-mode and Windows authentication
- The SQL account assigned for Apex Central should have:
- dbcreator permission for the server role is needed during installation
- Db_owner permission and DBO user account for the database role to the db_ApexCentral database
- Make sure that the latest Apex Central patch is installed.
- Check if Apex Central or Apex Central SQL DB is using the custom port or default port. For reference, refer to Ways to check if the Control Manager (Apex Central) SQL DB Server is using a Custom Port.
- Open an elevated Command Prompt.
- Change the directory to the ..\Control Manager\Dbconfig folder.
- Run the Dbconfig.exe tool.
Usage: DBConfig [options]
Use this tool to modify the database settings.
Options:
- DBName="database name" database name.
- DBAccount="database account" database account.
- DBPassword="database password" database password.
- Mode="SQL" authentication mode. SQL or WA.
- For DBHost="ip address/hostname" database ip address/hostname if using a default SQL port
- For DBHost="ip address/hostname,custom port number" database ip address/hostname if using custom SQL port
- DBHost="ip address/hostname" database ip address/hostname.
- Owner change owner to dbo.
Example:
DBConfig -DBName="db" -DBAccount="sqlAct" -DBPassword="sqlPwd" -Mode="SQL" -DBHost="10.1.152.124"
DBConfig -DBName="db" -DBAccount="sqlAct" -DBPassword="sqlPwd" -Mode="SQL" -DBHost="10.1.152.124,8433"Example:
DBConfig -DBName="db" -DBAccount="winAct" -DBPassword="winPwd" -Mode="WA" -DBHost="(local)"
Example:
DBConfig -DBName="db" -DBAccount="sqlAct" -DBPassword="sqlPwd" -Mode="SQL" -DBHost="(local)\SQLEXPRESS"
Example:
DBConfig -Owner
- Change the username and/or password of the account that Apex Central uses to access the database.
-
Set a DBO account for the Apex Central database.
The account assigned for Apex Central should have:
- dbcreator permission for the server role is needed during installation
- Db_owner permission and DBO user account for the database role to the db_ApexCentral database
- Password
- It can be a Windows account or SQL account
To change the DBO account of the database, execute the following command:
USE db_ApexCentral
Go
sp_changedbowner '<new db owner name>' - If you will use a new account, and will use "Windows Authentication" for SQL Login, make sure that the Windows account is a member of the built-in Local Administrators group. "Log on as a Service" and "Log on as a Batch Job" user rights are also needed. These are set in Step 3.
- Use the DBConfig tool to configure the new username and password.
Example:
DBConfig -DBName="db" -DBAccount="sqlAct" -DBPassword="sqlPwd" -Mode="SQL"
- This action/step will change the connection strings in ASP.net to local.
- Make sure to specify the DBO account associated with the database when using the DBConfig tool.
- The DBConfig tool is case-sensitive. Make sure to follow the parameter and values exactly.
- Make sure that DBName is specified as DBName, not "dbname". Also, if the database name on the SQL server is db_ApexCentral, it should be specified as db_ApexCentral, not "db_ApexCentral".
- When creating or changing the password for the Windows account, do not use any of the following characters: < > " ;.