SAM Pro OOB scheduled jobs performance issue when domains seperated

[Sujithra Govind]

In our domain-separated instances, SAM PRO has been set up within a specific domain. However, several out-of-the-box SAM Pro scheduled jobs are configured in the global domain. This setup, as it seeks data across each domain, is leading to performance issues within the instance.

(For example:

• SAM/CI - Populate Licensing Data
• SAM - Update Software Usage
• SAM - Discovery Model to Software Model Matching)

please clarify the following:

1. Was it intentional to configure OOB jobs in the global domain?
2. What risks might be involved if these jobs were moved to the domain configured for SAM Pro?

[Community Alums · Accepted solution]

Hi @Sujithra Govind ,

IT was intentional to configure jobs in global domain itelf.

We don't recommend domain separating any other system tables, and domain separation is not supported for Scheduled Jobs as all of the scheduled jobs are intended to run in the global scope.

[Community Alums · Accepted solution]

Hi @Sujithra Govind ,

IT was intentional to configure jobs in global domain itelf.

We don't recommend domain separating any other system tables, and domain separation is not supported for Scheduled Jobs as all of the scheduled jobs are intended to run in the global scope.

[Community Alums · Accepted solution]

Hi @Sujithra Govind ,

Also, Follow the best Practices :

https://www.servicenow.com/community/now-platform-blog/8-best-practices-for-supporting-domain-separa...