Database Footprint

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 12:19 AM
Hi Architects,
Need your suggestion & Best practice in order to reduce the size of "sys_journal_field" table.
I have tried reducing the size of task, audit and audit delete tables via table cleaner, but somehow I can see "sys_journal_field" table size is not reducing.
Can anyone provide the best practice to reduce the size effectively and as early as possible.
- Labels:
-
Architect

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 12:44 AM - edited 07-14-2024 12:44 AM
Hi there,
Journal Entries [sys_journal_field] don't have actual references to other records. It uses a Document ID field instead. Depending on how you have been cleaning up data, it might be that you Journal Entries table has orphaned records (which are basically useless). Have a look if that's also in your case.
Also remember, for database footprint (and performance!!!) just cleaning up data is not enough. You also need to have the tables rebuild:
- 2024-05-20 - Blog - Keeping your instance database footprint tidy (09): Reclaiming Table Free Space
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field