Pulse SQL DB Log size


We found SQL Log size grew much faster than expected, we are still under tracing some pulse issue, so pulse DEBUG mode is enabled for now, is it because of this?
(this is a UAT environment, assume there’s no too much activity, installed Pulse around one to two months ago)

Hi @vhsieh,

This is a good question. Pulse continuously writes to the database the size the summary of the current state of the TM1 Services and their hosting Server (Every 10 minutes by default). Despite having lots of transactions of not.

This would impact the Log in SQL. However, the size of the log can be managed by DBA, I suggest to refer to the following article from Microsoft for more details: