Migrating to MS SQL Server

Pulse v5.6 introduced support to MS SQL Server (2012 and onwards). This article describes the steps that you need to follow to configure Pulse with MS SQL Server.

Configure Pulse to use MS SQL Server

You can decide to move to MS SQL Server anytime after the upgrade but you should make sure first that Pulse is working with the new H2 database.

Instead of using H2, you can now ask Pulse to send the data into a centralized MS SQL Server database.

The advantage of using MS SQL Server is a better performance in larger Pulse DBs with concurrent active Pulse users.

When using MS SQL Server, it is recommended that each Pulse has its own database. Upgrading Pulse is a little bit more tricky when the same database is shared across multiple Pulse.

Enable MS SQL Server:

To Enable SQL Server, you need to do the following step:

Create a new database on your SQL Server called Pulse (ask your DB Administrator to do this)

Create a SQL Server login (user name / password) that has DB owner (DBO) access to the Pulse database.

Stop the Pulse services

Update SQL server settings in Pulse for TM1/conf/Pulse.cfg

[SQLServer]

JDBCURL = localhost:1433;databaseName=Pulse
UserName = {The SQL UserName}
Password = {The SQL password}

The password will be encrypted after Pulse restart.

Start the Pulse services

The first time you start the Pulse services, it is going to migrate the data from the docs.h2.db to the SQL server database. The time to migrate H2 to SQL server is approximately twice the time of the migration from Monitor.db to docs.h2.db.

Note: Pulse records the server name and the TM1 service name. Even if you have the same TM1 instance name in DEV, UAT and PROD, you will be able to differentiate the instances with the server name: