1. Run the CX Report Database Manager by selecting Start > All Programs > Tealeaf Technology > Tealeaf CX Report Server > CX Report Database Manager.

   When TDM is started, the Connect to Tealeaf Databases window is displayed.

2. To connect to the Tealeaf database, verify the connection information and the authentication mode and click Connect.
   TDM attempts to connect to the databases and gather general information about the databases.
   1. In the Authentication drop-down, select the type of user authentication to connect to the database.

      Option	Description
      Windows Authentication	Select this option if the Windows™ account running the TDM has administrator (sa) access to Microsoft™ SQL Server.
      Tealeaf Authentication	Select this option to run using the built-in Tealeaf SQL account. Note: After running the Database Manager to upgrade or install databases under Tealeaf Authentication, you must generate and run a permissions script that enables the appropriate permissions for the TLADMIN account. This script must be run as a SQL Server admin user. Note: The Tealeaf SQL account only has access to the Tealeaf objects within SQL server and cannot create new objects.
      SQL Server Authentication	Select this option to enter an SQL Server user name and password with administrator (sa) access to SQL Server.
      Local Access	Select this option to gain access to actions that do not require access to SQL Server.

   2. In the Network Protocol drop-down, you can select the connection type.
      Note: The Network Protocol setting you specify here must match the setting that is configured in SQL Server Management Studio. For more information, see the documentation that came with that product.

      Connecting options:

      • TCP/IP
      • Named Pipes

      Note: Shared Memory protocol is not supported by TDM.
   3. If needed, you can change the default command timeout. Values are in seconds.
   4. In the Reports Host field, enter the host name of the server hosting the reports databases (Reports, System, RS Extractor, Statistics). TDM attempts to auto-populate this field.
      Note: Depending on your license and the local database environment, a Product Registry Entry(s) Missing message may appear in the Host and Port fields for the corresponding database(s).
   5. In the Port field, enter the port SQL Server is configured to use.

      TDM attempts to auto-populate this field.

      Note: If you are not using the standard Tealeaf databases port (1433), this value must be also populated in the Report configuration.
   6. In the Search Host field, enter the host name of the server hosting the cxReveal database, if cxReveal is licensed.

      The cxReveal database is used to store session attribute information for cxReveal users. Additional installation and configuration is required.

   7. In the Port field, enter the port SQL Server is configured to use for the cxReveal database.

      TDM attempts to auto-populate this field.

      Note: If you are not using the standard Tealeaf databases port (1433), this value must be also populated in the Report configuration.
3. If you do not want to connect to the database or the database is not accessible, you can still make configuration changes by clicking Configure.
4. After verifying that the information is correct, click Connect. TDM attempts to connect to the databases and gather general information about them.

When you migrate during upgrade, you can elect to delete data. By default, data is deleted during migration to limit the overhead required to complete the operation. Before you begin, verify that you have a valid backup of the databases that you are migrating. If you do not delete during migration, the data from the previous version is retained, and all migration operations are performed within the database to copies of the data. If migration fails, your database remains intact. However, the size of your SQL Server database may become very large.

Before the installation of new databases, you can configure the general filegroup locations to be applied by default to each newly installed database and specific filegroup locations for individual databases.

For example, you might decide that filegroups for TL_REPORTS belong on a separate volume on the current system.

The default paths on this page are derived from any applied changes on the General Filegroups page.

To define custom file groups:

1. If you did not do so already, click the use custom filegroups check box. You can change the fields as needed.
2. Select the database to which you are applying the custom filegroups.
3. Specify the filegroups for the database in the provided area.
4. Click Apply Changes.
   Note: These changes are also automatically applied when you leave the Filegroups page or run an All Databases operation.

The TDM uses a statements-based method of creating and modifying individual databases. Any defined operation that is applied to a Tealeaf database is defined as a sequence of statements that are applied to the database.

• Only non-critical statements are displayed in this pane. When a non-critical error is encountered during a database operation, a message is logged and an entry is added to this pane before continuing with the database operation.
• Successful statements do not appear in this pane.
• A critical failure immediately terminates the operation. These errors are not reported in this pane.

When a database operation results in a non-critical failure, the statements that failed to properly run appear in the Failed Statements pane and may be exported into a SQL file. If the error that caused the statements to fail was corrected, you may re-execute the statements in the exported file to complete the operation.

When you migrate report data during upgrade, you can migrate the value lists for enumerated value events to dimensions in the current release.

• To enable report data migration, click the Migrate Report Data check box.
  Note: Depending on the size of your database, this operation may take significant time and impede performance on your instance of SQL Server. Run this operation during off-peak hours.
• You can include the reference data dimensions in the migrated report data. To include these dimensions, clear the Migrate report data without default dimensions.

Data from previous days that are stored in thecxReveal Search database is migrated after initial startup of the Attribute Indexing session agent.

This command can be run multiple times without issues.