1. Acquire the full specs of the box running the Reporting/SQL Server, including CPU, RAM, and information about each hard disk drive. Drive information should include number of drives, contents of each drive, and available disk space.
2. What version of Tealeaf are you running?
3. What is the traffic load? How many pages per day? How many events per page? How many pages per session?
4. Is the entire Portal sluggish or just certain functions in the Portal?
   Note: If the latter, the problem is likely caused by issues with the code or configuration of the individual functions.
5. Set Log Level = 9 and collect a day or two of TealeafReportingSvc.log messages to help with troubleshooting.
6. On the SQL Server, open Performance Monitor. Watch the Avg. Disk Queue and Page/Sec counters for 5 to 10 minutes. Are either of them consistently pegged through the roof?
   Note: Does Performance Monitor show much paging on the box? This may indicate that the Data Service is starved for memory.
7. How large is the TL_REPORTS database?

When you have the above information, open a support ticket.

When a non-critical statement failed during a database operation, an error message similar to the following is displayed in the output pane:

One or more errors occurred during the operation.
TL_REPORTS : There was an error executing the command list. | 
Incorrect syntax near 'o'. | At statement: 
CREATE INDEX IX_DB_GROWTH o dbo.DB_GROWTH (DTS, NAME) ON [PRIMARY]

One or more warnings occurred during the operation.
TL_REPORTS : A non fatal error has occurred while executing a CREATE_INDEX 
statement 19 TL_REPORTS : There was an error executing the command list

Each of the following statement types is considered to be non-fatal by the Database Manager. When any of these errors occur, a log entry is inserted, similar to the above, and the DBM continues processing the script.

TLDbmStatementType.GRANT
TLDbmStatementType.GRANT_DATABASE
TLDbmStatementType.CREATE_INDEX
TLDbmStatementType.ALTER_INDEX
TLDbmStatementType.DROP_INDEX
TLDbmStatementType.CREATE_PROCEDURE
TLDbmStatementType.DROP_PROCEDURE
TLDbmStatementType.ALTER_PROCEDURE
TLDbmStatementType.CREATE_FUNCTION
TLDbmStatementType.DROP_FUNCTION
TLDbmStatementType.ALTER_FUNCTION

Depending on your licenses and installed products, you might see the following message in the Host and Port field for one or more Tealeaf databases:

Product Registry Entry(s) Missing

This message indicates that the product registry keys for the listed database do not exist on the machine where the Database Manager is run. This situation may be caused by one of the following:

• The product was not installed locally yet, so the database does not yet exist. You cannot perform operations on the local database until you complete the product installation.
• The database is installed on a remote server. For databases installed on a different server, no such registry key exists. In this case, the message can be ignored for purposes of local installation.

Here is an example of the message:

An error occurred while executing the search.
<ServerName> - Error: (12029) A connection with the server could 
   be established 

SQL_Latin1_General_CP1_CI_AS

This setting is configured regardless of the collation setting in SQL Server, which presents a problem for international customers, specifically those in Europe.

The solution is to drop and reinstall the TL_SEARCH database through the Database Manager.

1. On the Portal Server, start the Database Manager.
2. From the TDM menu, select Mode > Database Setup > Single Database Mode.
3. Drop the Search (TL_SEARCH) database:
   1. From the Single Database Options screen, select Search from the Database drop-down.
   2. From the Action drop-down, select Uninstall.
   3. Click OK.

   The database is uninstalled.

4. Create the Search database:
   1. Use the Search database creation script, which is in the following location:

      
      <install_directory>\SQL\DBCreateScripts\CREATE_TL_SEARCH.sql
      

   2. Start the Database Manager.
   3. From the TDM menu, select Mode > Database Setup > Single Database Mode.
   4. From the TDM menu, select DB Creation > Create Databases so that the option is not selected.
   5. From the Single Database Options screen, select Search from the Database drop-down.
   6. From the Action drop-down, select Install.
   7. Click OK.

   The Search database is installed with the proper collation setting.

If you are performing further installation operations, you might want to re-enable the Create Databases option. From the TDM menu, select DB Creation > Create Databases so that the option is selected.