Troubleshooting Transform Map Performance.

[deanproctor]

Some question to check issues with performance.
1. In the table transform map is the box checked for Run business rules? If so uncheck and run it again to see if the performance increases.
Note: Do not run items like business rules, workflows, approval engines, and so on during a transform unless you want all insert and update business rules, notifications, and workflows to run. For example, when importing all data from an old system, you may not want notifications to run. To disable these items from running and to cease auditing and field normalization within the transform map for that import, deselect the Run business rules check box.

2. Is the import a repeat of data if so this can lead to skipped rows. If yes:
If you are running a JDBC import, use the last run datetime option in your import set Data Source. For a type of File import, be sure that whatever is generating your files is only adding data that is new, or has been changed

3. Are you coalescing on non-indexed fields? If so
If possible, you should coalesce on a field that unique and already indexed. To determine if a field is already indexed, navigate to System Definition > Tables & Columns and find the table. In the list of columns for that table, an indexed column has a blue icon with an i next to it if indexed. For assistance indexing a field contact ServiceNow Technical Support.

4. Are you running imports at the same time as this one. If so stagger them so they do not overlap

5. Is the Import Set Deleter job running? If not. :
This is a size issue. If the import sets are not cleaned on a regular basis (a cleanup is recommended after seven days worth of data) the table fills causing imports to stop.

How to avoid this: Verify the Import Set Deleter job is running. If it is not currently running, contact customer support as they will truncate all import set tables before enabling this job.

6. How large is the data set that is being imported?

Thank you 

DeanP