Since Pulse v5.6, you can choose to use MS SQL Server (2012 and onwards) instead of the default H2 database. To learn how to migrate to MS SQL Server you should check the following article:

• Pulse Database Migration into MS SQL Server

Once you have created the new Pulse database into MS SQL Server, you need to add the MS SQL Server information to the Pulse configuration file (Pulse for TM1confPulse.cfg).

If you want to use SQL Authentication, you need to update the JDBCURL, Username and Password:

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

To configure Pulse to set up Windows Authentication with SQL Server, there are two ways to do it:

1. Stop Pulse services
2. Pulse for TM1 services need to run with the DB owner login of the MS SQL Server database.
3. Update the JDBCURL setting in Pulse.cfg
   JDBCURL = localhost:1433;databaseName=TM1Pulse;integratedSecurity=true
4. Download the sqljdbc_auth.dll
5. Add the file sqljdbc_auth.dll to C:WindowsSystem32 folder
6. Start Pulse Services

When you use integrated login, you don’t need to setup username and password in the Pulse.cfg, you just need to update the JDBCURL setting:

• JDBCURL = localhost:1433;databaseName=TM1Pulse;integratedSecurity=true
• UserName = 
• Password =

1. Stop Pulse services
2. Pulse for TM1 services need to run with the DB owner login of the MS SQL Server database.
3. Update the JDBCURL setting in Pulse.cfg
   JDBCURL = localhost:1433;databaseName=TM1Pulse;integratedSecurity=true;authenticationScheme=JavaKerberos
4. Start Pulse Services