The filegroup reference information in this section applies to new installations of the databases for Tealeaf Release 8.0 or later. Filegroups for upgraded versions of the databases reflect the earlier version's layout with new filegroups added, based on the new scheme.
Session Segment database
This database contains analytical data that is parsed from sessions that are
identified by Tealeaf users through the Portal Search and session segment analysis functionality.
The data is used to provide in-depth analysis of groups of sessions pertaining to a particular issue or event.
Filegroups
Filegroup
Description PRIMARY
Used for short-term storage and for the storage of small lookup tables.
DATA Stores the analytic data that is used for session segment analysis.
INDEX Non-clustered index storage.
Sizing
This database can be fairly large. Its size is dependent on the number and size of session segments being analyzed. If session segment analysis is not being used, this database should experience no growth.
Visitor Staging database
The Visitor Staging database contains the raw data that is extracted from sessions in the Tealeaf canisters.
The data is extracted into this database to provide flexibility in other ETL
operations and to separate those operations from the reporting capabilities of IBM Tealeaf cxResults.
Filegroups
Filegroup
Description PRIMARY
Contains basic database configuration and SQL Server information.
VISITOR
Contains the unique visitor information that is extracted from the canister sessions.
VISITORINDEX
Contains index information for the tables in the Visitor filegroup.
SESSION
Contains the raw session information that is extracted from the Tealeaf canisters.
SESSIONINDEX
Contains index information about the tables in the Session filegroup.
EVENT Contains the raw event data that is extracted from the Tealeaf canister sessions.
EVENTINDEX
Contains index information about the tables in the Event filegroup.
DATA Look up and Index data for the VDB extract process
Sizing
Under normal operation the Staging database contains only one week of
information. Assuming that traffic levels on the website remain relatively constant, this database should reach a stable size and remain relatively unchanged. The actual size of the database can be fairly large and varies depending several factors.
Refer to the database sizing section for further details.
Visitor Reporting database
The Visitor Reporting database contains a snapshot of the visitor data that is contained in the Tealeaf canisters.
This data supports the search and reporting capabilities IBM Tealeaf cxResults application. The data is loaded through an ETL process from the Staging database.
Filegroups
Filegroup
Description PRIMARY
Contains basic database configuration and SQL Server information.
DATA Contains the segment information that is generated through searches in the IBM Tealeaf cxResults application.
LOOKUP Contains largely static lookup information for use in reporting (for example, event definitions, reference information, and so on).
VISITOR
Contains all unique visitor information.
SESSION
Contains all the extracted session information.
EVENT Contains all the information about events the fired in the customers system.
INDEX Contains all the indexes for the database.
Sizing
The reporting database contains a snapshot of the visitor information that passes through the customers website. The time interval of the snapshot is configurable and is typically 2 - 3 months. As a result, this database can be quite large, but its size should stabilize after the first time interval. At that point, the snapshot
functions like a rolling window, removing older data and replacing it with current data. For exact sizing information, refer to "Database Sizing" in the IBM Tealeaf Databases Guide.
Reports
Tealeaf captures statistical information from these databases, which is available through the Portal.
v See "System Status" in the IBM Tealeaf cxImpact Administration Manual.
v See "System Status" in the IBM Tealeaf cxImpact Administration Manual.
cxResults Visitor database
This section provides some overview information about the IBM Tealeaf cxResults databases.
Overview
The Visitor database included with IBM Tealeaf cxResults captures and retains detailed information about individual visitors and their activities on your website and enables you to make direct queries of that data.
Hosted in Microsoft SQL Server, this relational database allows Portal- and script-driven access to visitor data, which greatly enhances the reporting reach of the Tealeaf system.
Note: As of Release 8.8, IBM Tealeaf CX requires SQL Server 2008 or later. Before you install or upgrade your database, review the instructions for managing the SQL Server upgrade first. See "Upgrading SQL Server for Tealeaf" in the IBM Tealeaf Databases Guide.
Prerequisites
The Visitor database can be installed in the same SQL Server instance as IBM Tealeaf CX databases, or you can install it in a separate instance.
v If you are installing IBM Tealeaf cxResults in a separate instance, you should review the pre-installation requirements. See "CX Pre-Installation Checklist" in the IBM Tealeaf CX Installation Manual.
Note: Whether you are installing in the same system as the IBM Tealeaf CX databases or in a separate system, you should review the database server requirements, which recently changed and may be different from when you initially installed. See "CX Pre-Installation Checklist" in the IBM Tealeaf CX Installation Manual.
Administration reference
Before you begin installation, you should review the advanced administration topics in the IBM Tealeaf cxImpact Administration Manual to learn the required logins, storage requirements, backup strategies, and other useful information.
See "Database Administration" in the IBM Tealeaf Databases Guide.
v For more information about the specific databases, filegroups, and their sizing requirements that are provided with IBM Tealeaf cxResults, see "cxResults Databases" in the IBM Tealeaf Databases Guide.
The IBM Tealeaf cxResults database schema is published online. See "Visitor Database Schema" in the IBM Tealeaf Databases Guide.
Installation
The Visitor database can be installed through the Tealeaf Database Manager, an external utility that can be used to install one or more Tealeaf databases, including the generation of required permissions scripts for the database users.
Permissions
The Tealeaf Database Manager requires specific permissions to install Tealeaf databases.
Upgrading
If you are installing the Visitor database as part of an upgrade of your Tealeaf system, the Tealeaf Database Manager handles most upgrades seamlessly.
Depending on your configuration, you may be required to install in Advanced mode, which requires extra manual steps.
Dimensional data
Note: The use of dimensional data in IBM Tealeaf cxResults is not supported in this release.
Beginning Installation
When you are ready to begin your installation, launch the Tealeaf Database Manager.
Related concepts:
“Database manager SQL Server access and permission requirements” on page 22 Related reference:
Chapter 4, “Using Tealeaf Database Manager,” on page 41
“Migrating Tealeaf databases” on page 36
Chapter 3, “Installing Tealeaf databases,” on page 13
Troubleshooting
You can troubleshoot if you encounter difficulties during the installation or upgrade of the Visitor database.
Related reference:
“Troubleshooting Tealeaf databases” on page 81
Visitor Database Schema
Tealeaf publishes a set of views in the Visitor Reporting database to facilitate custom reports and queries against the data. These views will be maintained in future releases regardless of underlying schema changes.
Note: It is strongly recommended that any custom reports or queries reference the views and avoid directly referencing the underlying tables.
Table 5. Visitor Database Schema
View Name Description Columns
VW_DATASET Lists the current segments in the database along with their sessions and a count of how many times each session matched the search terms.
ID, VISITOR_ID, SESSION_ID, MATCH_1, MATCH_2, MATCH_3, MATCH_4
VW_EVENT Returns the list of all regular event occurrences for sessions currently in the database.
ID, TIMESTAMP, VISITOR_ID, SESSION_ID, UNIQUE_ID, URL, PREV_URL, SERVER, HOST, APP, HIT_NUMBER, VALUE
Note: Beginning in Release 8.0, the structure of Tealeaf events changed. To maintain consistency with previous versions of IBM Tealeaf cxResults, the columns in VW_EVENT remain unchanged.
In Release 8.0 and later, however, the following columns contain null values:
UNIQUE_ID, PREV_URL, SERVER, HOST, and APP.
VW_NUMERIC_EVENT Returns the list of all numeric event occurrences for sessions currently in the database.
ID, TIMESTAMP, VISITOR_ID, SESSION_ID, UNIQUE_ID, URL, PREV_URL, SERVER, HOST, APP, HIT_NUMBER, VALUE
VW_REPORTS Returns the list of defined visitor report types. Any report added using the steps for creating a custom report should appear in this view.
ID, IDENTIFIER, DISPLAY_NAME, CUSTOM, FORMAT, STORED_PROCEDURE
VW_SESSION Returns the list of sessions currently contained in the Visitor database.
CANISTER_SESSION_ID, TLTSID, START, END, LENGTH, REPEAT_VISIT, PAGE_COUNT, REQUEST_SIZE, RESPONSE_SIZE, IP, LOGIN.
USERDEF1, USERDEF2, USERDEF3, USERDEF4, FIRST_PAGE, LAST_PAGE, REFERRER, BROWSER, HOSTNAME, FILE
VW_SESSION_ATTRIBUTE Returns session attribute data. v SESSION_ID- Database session ID for joining to session and event data v CANISTER_SESSION_ID- The session ID
from the Canister
v TLTSID- the session's TLTSID
v ATTRIBUTE_ID- The database ID for the session attribute
v ATTRIBUTE_TYPE- T for text attributes; N for numeric attributes
v ATTRIBUTE_VALUE- The value
represented as a sql_variant. Based on the ATTRIBUTE_TYPE column, it can be cast to either NVARCHAR or FLOAT.
v HOSTNAME- The server name of the Canister
v FILENAME- The Canister file containing the session
Table 5. Visitor Database Schema (continued)
View Name Description Columns
VW_SESSION_EVENT Returns the same list of sessions as VW_SESSIONwith the addition of a comma separated list of event UNIQUE_ID values.
This view is less efficient than VW_SESSION and should only be used when the event list is required.
CANISTER_SESSION_ID, TLTSID, START, END, LENGTH, REPEAT_VISIT, PAGE_COUNT, REQUEST_SIZE, RESPONSE_SIZE, IP, LOGIN, USERDEF1, USERDEF2, USERDEF3, USERDEF4, FIRST_PAGE, LAST_PAGE, REFERRER, BROWSER, HOSTNAME, FILE, EVENT_UNIQUEIDS VW_VISITOR Returns data on the list of visitors in the
database.
ID, VISITOR_ID, FIRST_VISIT, LAST_VISIT, LOOKUP
VW_VISITOR_STATISTICS Returns database wide statistics grouped in hour intervals.
UNIQUE_VISITORS, TOTAL_VISITS, ONE_HIT_VISITS, NEW_VISITS, REPEAT_VISITS
Examples
This section provides some examples of views that were created by using the visitor database schema.
Retrieve a list of the top IP addresses for a segment
The variables @top and @dataset must be defined or substituted for numeric values.
SELECT TOP(@top) s.IP IP, count(s.ID) [COUNT]
FROM VW_DATASET ds
JOIN VW_SESSION s on s.ID = ds.SESSION_ID WHERE ds.ID = @dataset
GROUP BY s.IP
ORDER BY [COUNT] DESC;