![Comment_Icon_black](https://blog.octanesolutions.com.au/hubfs/Imported_Blog_Media/Mode_Comment_Icon_black%20(1).webp)
![Comment_Icon_black](https://blog.octanesolutions.com.au/hubfs/Imported_Blog_Media/Calendar_Regular_Icon_1%20(1).webp)
![Alarm_Icon_1](https://blog.octanesolutions.com.au/hubfs/Imported_Blog_Media/Alarm_Icon_1%20(1).webp)
Gone days, where we had no control/alerts mechanism on the TM1 database, CPU/memory it consumes, react at the nick of the moment before TM1 server crashes. I am sure all TM1 lovers, administrators and business users who had these experiences in the past would connect to what I am referring to. For all new Planning Analytics users, in earlier versions of TM1/ Planning Analytics, we had little overview on how much on RAM/ memory can a TM1 instance use/utilize or have an inbuilt alter mechanism. TM1 Database Alert Mechanism: Issue: Most of you know, TM1 Server loves memory/RAM, more memory ...
![Line_2015](https://blog.octanesolutions.com.au/hubfs/Imported_Blog_Media/Line%2015-svg%20(1).webp)