Best practice for iterating through a table with the Table API
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hello everyone,
I’m working on an integration where I need to iterate through a large table (for example, incident) using the REST Table API. My goals are:
To get responses as quickly as possible (low latency per page).
To avoid over-consuming instance resources (not put unnecessary load on the DB or the node).
Right now, I’m paging through the records with sysparm_limit and either sysparm_offset or keyset style queries (e.g., ORDERBYsys_id + sys_id>{last} watermark).
Before I settle on an approach, I’d like to ask the community:
* What’s considered best practice for iterating through large ServiceNow tables via API?
* Are there recommendations on page size (sysparm_limit) that balance speed with instance impact?
* Is keyset pagination (using sys_id or sys_updated_on) preferred over using sysparm_offset?
* Are there any other tips to ensure I’m getting the data efficiently without overloading the instance?
Thanks in advance for any guidance!
0 REPLIES 0