- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 02:36 AM
Hi Team,
We are currently working on a integration project where a read access to be provided on incident_metric table(View). This view has around 10 Million records as of now. The data will be pushed to a database where the data is been used by a XYZ tool for sentiment analysis.
Is that a good practice to create a Table API over this view ? Since we have 10 M records will it create performance issues ?
If we are to provide read access on this view how many records for transaction can we provide to database team ?
Regards
Siva Teja
Solved! Go to Solution.
- Labels:
-
Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 03:05 AM
Schedule load job from DB team to ServiceNow. ServiceNow is just exposing data. Now, pull & related job is on DB team.
When an read access is given to DB team via table API they can pull it round the clock as per my understanding. -- Yes, but I don't think there will be a need to execute it mulitple times during the day. Also, as it will be scheduled DB team will also like to avoid manual job execution. No need, to action or control. All that is needed is agreement between teams.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 03:05 AM
Schedule load job from DB team to ServiceNow. ServiceNow is just exposing data. Now, pull & related job is on DB team.
When an read access is given to DB team via table API they can pull it round the clock as per my understanding. -- Yes, but I don't think there will be a need to execute it mulitple times during the day. Also, as it will be scheduled DB team will also like to avoid manual job execution. No need, to action or control. All that is needed is agreement between teams.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 03:14 AM
Thanks for your elaborated answer. I am happy to mart it as correct and helpful answer. before we close the discussion I have 2 final questions
1. What is the maximum number of records we can expose in table API without affecting performance of the system ?
2. Do we have a code for DB team for coping the records for that day from incident_metric table.
Regards

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2022 03:26 AM
1. What is the maximum number of records we can expose in table API without affecting performance of the system ?
Well, that is difficult to answer as it might depend on data load, number of columns, etc. However, per page it is 10k records but should not have that performance impact as it will on specific node & not all nodes.
2. Do we have a code for DB team for coping the records for that day from incident_metric table.
No need of code. You need to share API detail accordingly. Something as below
https://instance-name.service-now.com/api/now/table/incident_metric?sysparm_query=mi_sys_created_on%3E%3Djavascript%3Ags.beginningOfYesterday()&sysparm_limit=1
where incident_metric is table & text in red is query for records after yesterday.
You can do the same by navigating to REST API Explorer from application navigator & select appropriate table & apply required query. You can apply filter on incident_metric table & then copy the query & past it in the sysparm_query field on the REST API Explorer