- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2016 01:05 PM
We have an issue where some of our admin users can't access the sys_audit table. For these users it always times out. Other admin users with the same group and roles are able to view the table and it takes less than 20 seconds to pull up. All of the response delay is server side and switching CPUs doesn't matter. I assume this is a user preference issue but can't figure out which preference it would be.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2016 08:02 AM
I would imagine it is related to the users default sorting on the table. Under user preferences, check for sys_audit.db.order & sys_audit.db.order.direction, and delete those properties.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2016 10:20 AM
Audit tables are HUGE. The database not only has to UNION them all together, it then needs to sort them by what is an un-indexed column. There's nothing you can do about performance on that. I know at one point our audit tables consisted of >90% of the data in our database due to some very bad fields being audited, we had to work with Service-now to clean them up after turning off some of the auditing.
I 'never' look at the sys_audit table directly. The table is in a rotation that generates a new table every 30 days. If you go to tables, and filter by table name sys_audit, you'll see a bunch of tables sys_audit0001, sys_audit0002.
Find the last table created, subtract one, and look at that table (the current table being used, the next table is always there and ready to go for when it is its turn), and do a .list on that table. Much more managable. I can then back-track if I want to look at data from 3 months ago, subtract 4 from the last table and look at that one.
