SQL server database for Pulse

We’ve got two questions from a Pulse client that switched to SQL server. Could you please assist?

  1. How Pulse will behave in case of :
    a. SQL database server overload (for example, in case of operating system update or other updates on the server)?
    b. losing network connection with SQL server?
  2. Is it possible to get Flow Chart information in SQL database somehow (they want to use it in Power BI to build their own charts)?


Hi @ssarvartdinova,

When you configure Pulse to use SQL Server, Pulse will migrate data from its current local database to the new database in SQL server. Pulse will then only use the database in SQL Server. Having access to SQL server is critical for Pulse, If Pulse looses connection to SQL Server for whatever reasons (operating system update, losing connection with SQL Server…), Pulse will stop working.

I hope this help.



Hi @ssarvartdinova,

The Relation table has a summary of relationships between TM1 objects.

@Vincent @tryan Thank you!
One more question:
Is there any definition of data model / list and description of tables of Pulse database?

Hi @ssarvartdinova,

There isn’t a diagram available to share but if you have any specific questions please ask on the forum.

What are you trying to achieve? If you are interested by specific data, we can tell you which table you should look at.



Hi @Vincent and @tryan,

I just had a chat with the client and what they are trying to do is to use Pulse SQL DB as a source to Power BI reports/dashboards. They want to customize our Pulse auto-generated Flow Chars using Power BI.

So then they’d expect Power BI reports to be automatically updated based on changes in the model (depending on documentation update).

Do you foresee any concerns from a technical angle (or sustainability) and is there any case who have implemented such an approach?


Hi @ubozkurt,

I am not familiar with Power BI so can’t help you out with that.