Pulse Data

Cubewise Pulse collects and stores a wide range of data about your IBM Planning Analytics (TM1) environments. This section explains what Pulse stores, where it is stored, and how to configure, access and maintain it.

Where Pulse stores its data

Pulse uses three storage layers:

Storage	What it holds	Best for
Relational database - H2 (default), MS SQL Server or Postgres (Pulse 7.2+)	Pulse configuration, model documentation, change tracking metadata (who changed what and when), cube statistics, TM1 Web and Excel tracking, migration packages	Structured queries and Pulse web client features
VCS folder - `<Pulse Install Directory>\vcs\git\<environment>\<instance>`	One Git repository per TM1 instance, holding each tracked object (processes, rules, dimensions, etc.) as a file with its full change history	Change tracking, object comparison and rollback. See How to Clean the VCS Folder to manage its size
Opensearch (Pulse 6+)	Second-by-second monitoring data: server state, TM1 logs, process and chore history, sessions, user and object history, alerts	Time-series queries and Pulse Explorer dashboards

Sensitive data such as cube content included in migration packages is encrypted using the Pulse encryption key.

What Pulse stores

Category	Data
System monitoring	CPU, memory, disk and uptime; active sessions and connection details; running chores and TI processes; TM1 server logs
Change tracking and model metadata	Changes to rules, feeders, dimensions, subsets and processes; object relationships for impact analysis; automatically generated model documentation
User and license analytics	Who accessed which application, when and for how long; license usage and optimization reports
Migration and DevOps	Migration packages (metadata and optionally encrypted cube data); rollback information
Performance and history	Second-by-second performance history; alert and health check history

Pages in this section

Understanding the data

Page	Description
Supported Databases	The relational databases Pulse supports (H2, MS SQL Server, Postgres) and how to configure each one
Understanding Pulse Opensearch Data	What is stored in Opensearch, how indices are organised and how to access the data

Moving to another database

Page	Description
Migrating to MS SQL Server	Steps to move the Pulse database from H2 to MS SQL Server
Migrating to Postgres: Steps and Requirements for Pulse 7.2+	Steps to move the Pulse database from H2 or MS SQL Server to Postgres

Configuring the SQL Server connection

Page	Description
Connect to SQL Server Using Windows Authentication	Use the Pulse service account (integrated security) instead of SQL credentials
Managing the Database Connection Pool	Tune the [DBConnectionPool] settings for MS SQL Server

Querying the Pulse database

Page	Description
Connecting to the Pulse Database	Browse and query docs.h2.db using the H2 console or a JDBC client such as DBeaver
Connecting to the Pulse Database through an ODBC Driver	Query Pulse data with SQL through the built-in PostgreSQL interface and an ODBC DSN

Maintaining the data

Page	Description
Cleansing the Pulse data	Use the [Maintenance] job to limit how much history the database and Opensearch keep
Changing the frequency of the Pulse Elasticsearch indices	Change index patterns (yearly, monthly, daily) to reduce Opensearch disk usage

For developers

Page	Description
Database Connections (H2 & SQL Server)	Connecting to the H2 and SQL Server databases in a development environment