# Perspective Alarm Journal table freezes in 8.1.0-rc1

**URL:** <https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060>\
**Category:** Ignition Early Access\
**Tags:** perspective\
**Created:** [October 27, 2020, 5:19pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060 "2020-10-27T17:19:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![arun1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arun1/32/79753_2.png) [@arun1](https://forum.inductiveautomation.com/u/arun1)\
**Post date:** [October 27, 2020, 5:19pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060/1 "2020-10-27T17:19:57Z")

</div>

I am using Ignition 8.1.0-rc1 and the Perspective Alarm Journal table is not able to pull more than 2,700 records from alarm\_events table in the DB. If I choose a large enough date range (in both realtime and history mode) then 0 results are returned and the table hangs up, Designer become unresponsive, and Perspective session in a browser freezes as well. The OS is Server 2016 Datacenter and has SQLExpress as the DB in the same VM (Intel Xenon, 2.2 GHz (2 processors) with 12GB RAM).  
Alarm Journal table in Vision and regular table in Perspective (fed by a Named Query with a simple SELECT statement from alarm\_events table) also has this seemingly arbitrary limit of 2,700 returned records.

However if I install Ignition 8.1.0-rc1 on a VM (Intel Xenon, 2.4 GHz (4 processors) with 16GB RAM) with Server 2019 Std as the OS then the Perspective Journal table functions normally, i.e. it is able to pull as much as 18k rows in an instant!

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 27, 2020, 5:53pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060/2 "2020-10-27T17:53:07Z")

</div>

Check the alarm journal table(s) for index fragmentation.

---

<div class="post-metadata">

**Author:** ![arun1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/arun1/32/79753_2.png) [@arun1](https://forum.inductiveautomation.com/u/arun1)\
**Post date:** [October 27, 2020, 6:05pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060/3 "2020-10-27T18:05:01Z")

</div>

Is that a configuration or check box in the Perspective Alarm Journal? or something to check in the SQL table like the ‘id’ column having unique values etc?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 27, 2020, 8:51pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-journal-table-freezes-in-8-1-0-rc1/40060/4 "2020-10-27T20:51:20Z")

</div>

Something to check in MSSQL for the `alarm_events` and `alarm_events_data` tables.