Prepare to Install › Central Management Server Database Requirements and Preparation › Use a Supported Database Server › Set up an Empty Database for the CMS

Set up an Empty Database for the CMS

If you want to use an existing database server as the CMS or auditing database, create a tablespace or database before installing BusinessObjects Enterprise.

If you use your own database during the installation of BusinessObjects Enterprise, the installer prompts for the connection and authentication details. The following database servers are supported for the CMS system and audit databases:

• Microsoft SQL Server (ODBC) (Windows only)
• Oracle
• DB2
• SQL Anywhere
• MySQL
• Sybase

To integrate your existing database with BusinessObjects Enterprise, prepare it. Here is a summary of the steps to prepare your database:

1. Create a tablespace, schema, or database (the exact terminology depends on the database platform you are using) to act as the CMS database. Create another database for the auditing database, if you plan to enable auditing (or you can use the same database for auditing purposes).
2. Create a user account and password that BusinessObjects Enterprise can use to access the CMS database. Create another username and password if you plan to enable auditing.
3. Grant privileges to the user to create, modify, and delete tables and create procedures.
4. Record the names of the databases, the user accounts, and the passwords that you created. Then you can enter the details when you run the BusinessObjects Enterprise installer.

During the installation, you can reinitialize the existing database. This action creates tables in your existing database. See your specific database server documentation if you are unsure of the procedure for creating a tablespace, schema, or database. Ensure that your database server is set up to use Unicode character encoding (such as UTF-8).

Important! You cannot use a database from a previous release for BusinessObjects Enterprise. With custom installation, you must create a database, or the existing data from the previous release is destroyed. To migrate from a previous release, create a database before the installation of CA Business Intelligence. The installer can manage the migration (if you select the option) or you can perform the migration manually after installation.