Below are instructions for setting up table compare in different situations:

ServiceNow to ServiceNow table compare

There are two options when it comes to comparing tables between two instances of ServiceNow:

• Audit Shares looks at the records that have been bulk shared and compare them to the records in another instance. This is useful for ensuring that bulk shares are captured in the subscribing instance properly. 
• Compare Records by Table looks at records that satisfy specified conditions and compares them with the same records in another instance. This is useful if you have multiple dynamic/bulk shares on the same table and want to verify that the cumulative sharing of records is captured properly in the database.
  

↑ Go to top of page

Audit shares

The Audit Shares option compares the records shared by bulk shares with the records in another ServiceNow instance. This is useful for ensuring that bulk shares are captured in the database properly.

1. Follow the steps to create a bulk share or go to a bulk share that you want to compare at Perspectium > Perspectium Core > Shares > Bulk Share.
   
   
2. On the bulk share page, switch to the Standard view.
   
   
3. In the Advanced tab, in the Runtime Settings section, check the Enable confirmation box. 
   
   
4. Click Update, and the table compare will automatically occur once the the bulk share has been executed. Now that the bulk share is ready, you can go back into the Tools module.
   
   
5. Go to Perspectium > Perspectium Core > Tools, and click Table Compare: ServiceNow to ServiceNow, and then Audit Shares.
   
   
6. In the resulting list of all your bulk shares, select the ones that you want to use in the table compare. Make use of the Select All and Deselect All options to easily select or deselect many bulk shares at once. 
   
   
7. Click Run Table Compare to start executing the table compare. Or, click Schedule Table Compare to have the table compare configuration run on a scheduled basis.

Compare records by table

The Compare Records by Table option compares the records that satisfy specified conditions with the same records in your database. This is useful if you have multiple dynamic/bulk shares on the same table and want to verify that the cumulative sharing of records is captured properly in the database. 

1. Go to Perspectium > Perspectium Core > Tools > Table Compare: ServiceNow to ServiceNow > Compare Records by Table. 
   
   
2. On the resulting page, select a table from the Choose Table dropdown.
   
   
3. Use the Comparing Setup dropdown to select the records that you want to compare. This is where you can specify whether you want to compare the base table records only, or include the child records of that table as well. You can find information on child tables and the general table hierarchy here.
   
   
4. In the Bulk share field, select a bulk share that will mimic the configurations for re-sharing missing records. 
   
   
5. (Optional) Create a condition with the condition builder or leave it blank to select all records from the chosen table. If the bulk share selected contains conditions, the condition builder will be pre-filled with the same conditions. 
   
   
6. Click Add to add the table and condition to the active table compare configuration.
   
   
7. Click Run Table Compare to start executing the table compare. Or, click Schedule Table Compare to have the table compare configuration run on a scheduled basis.

ServiceNow to database table compare

This module allows you to compare records shared via bulk or dynamic shares with tables in another database. With bulk shares, a list of sys_ids will be sent from ServiceNow to the DataSync Agent for the Agent to check if the records with the corresponding sys_ids exist. If there are discrepancies, a message will be sent back to ServiceNow and the missing records will be re-shared to the Agent. This process will repeat until all records have made it to the target database.

Table Compare can also compare deleted records that dynamic shares share out to delete in the database. The Agent will check to make sure that the sys ids in the list do not exist in the database. The records that should have been removed but was not previously removed will be deleted immediately.

Here are the supported databases for table compare:

*These versions of the associated databases have been tested at this time but in general these databases will work with Table Compare.  Testing is ongoing to support more databases.

<most_recent_record_query>SELECT sys_id FROM %s WHERE sys_id = "%s" AND %s = "%s"</most_recent_record_query>

<most_recent_record_query>SELECT sys_id FROM %s WHERE sys_id = "%s"</most_recent_record_query>

There are three options when it comes to comparing tables between a ServiceNow instance and another database:

• Audit Shares looks at the records that have been bulk shared and compare them to the records in the database. This is useful for ensuring that bulk shares are captured in the subscribing instance properly. 
• Compare Records by Table looks at records that satisfy specified conditions and compares them with the same records in the database. This is useful if you have multiple dynamic/bulk shares on the same table and want to verify that the cumulative sharing of records is captured properly in the database.
• Synchronize Delete Records looks at records that no longer exist in your instance and remove them from your database.

Audit shares

The Audit Shares option compares the records bulk shared by a ServiceNow instance with the records in your database. This is useful for ensuring that bulk shares are captured in the database properly.

1. Follow the steps to create a bulk share or go to a bulk share that you want to compare at Perspectium > Perspectium Core > Shares > Bulk Share.
   
   
2. On the bulk share page, switch to the Standard view. 
   
   
3. In the Advanced tab, in the Runtime Settings section, check the Enable confirmation box. 
   
   
4. Click Update, and the table compare will automatically occur once the the bulk share has been executed. Now that the bulk share is ready, you can go back into the Tools module.
   
   
5. Go to Perspectium > Perspectium Core > Tools, and click Table Compare: ServiceNow to Database, and then Audit Shares.
   
   
6. In the resulting list of all your bulk shares, select the ones that you want to use in the table compare. Make use of the Select All and Deselect All options to easily select or deselect many bulk shares at once. 
   
   
7. Click Run Table Compare to start executing the table compare. Or, click Schedule Table Compare to have the table compare configuration run on a scheduled basis. When choosing the Schedule Table Compare option, a scheduled job will be created with the name Perspectium Scheduled Table Compare and you can go to Perspectium > Control and Configuration > All Scheduled Jobs to view and modify this job. Each time you select the Schedule Table Compare option, it will create a new scheduled job with the Perspectium Scheduled Table Compare name.

Compare records by table

The Compare Records by Table option compares the records that satisfy specified conditions with the same records in your database. This is useful if you have multiple dynamic/bulk shares on the same table and want to verify that the cumulative sharing of records is captured properly in the database. 

1. Go to Perspectium > Perspectium Core > Tools > Table Compare: ServiceNow to Database > Compare Records by Table. 
   
   
2. On the resulting page, select a table from the Choose Table dropdown.
   
   
3. Use the Comparing Setup dropdown to select the records that you want to compare. This is where you can specify whether you want to compare the base table records only, or include the child records of that table as well. You can find information on child tables and the general table hierarchy here.
   
   
4. In the Bulk share field, select a bulk share that will mimic the configurations for re-sharing missing records. 
   
   

5. (Optional) Create a condition with the condition builder or leave it blank to select all records from the chosen table. If the bulk share selected contains conditions, the condition builder will be pre-filled with the same conditions. 
   
   

6. Click Add to add the table and condition to the active table compare configuration.
   
   
7. (Optional) A table will appear for you to edit or remove the table you just added. In this table, check the Sync Deletes checkbox to remove records that no longer exist in your instance from your agent database.  
   
   
8. Click Run Table Compare to start executing the table compare. Or, click Schedule Table Compare to have the table compare configuration run on a scheduled basis. When choosing the Schedule Table Compare option, a scheduled job will be created with the name Perspectium Scheduled Table Compare and you can go to Perspectium > Control and Configuration > All Scheduled Jobs to view and modify this job. Each time you select the Schedule Table Compare option, it will create a new scheduled job with the Perspectium Scheduled Table Compare name.

 NOTE: Table compare results will be shown in the Previous Table Compare Executions table at the bottom. You can filter the results displayed in this table by the target type (Agent, Meshlet, ServiceNow, etc.). However, the target type isn't populated until the target responds back to ServiceNow with results. Prior to the results returning, the table compare result will show as Pending Response to indicate we're pending a response from the target and you can filter the results for those Pending Response as well. Further details on Previous Table Compare Executions can be found in the View and report table compare results section below.

Synchronize deleted records

Enabling this feature will send a message to your agent database to start comparing which records were deleted. Once the deleted records are detected, a series of delete messages will be sent. 

Here's how:

1. Go to Perspectium > Perspectium Core > Tools > Table Compare: ServiceNow to Database > Synchronize Deleted Records. 
   
   
2. On the resulting page, use the Choose Table dropdown to select the table that you want to use.
   
   
3. Use the Bulk Share field (and the magnifying glass) to select the bulk share that your Synchronize Delete can mimic for configurations. 
   
   
4. Click Add.
   
   
5. Click Run Table Compare to start executing the table compare. 

 NOTE: Since the deleted records will not be able to be queried once they've been deleted from the database, the Previous Table Compare Executions table for deleted records will show a state of Completed once the Perspectium application in ServiceNow has received the list of records in the database back from the Agent/Meshlet and processed this comparison and sent out any delete messages. 

↑ Go to top of page

View and report table compare results

After running a ServiceNow to Database table compare, you can view your results, including the total records compared, records not found in the target database that were shared by the ServiceNow instance or the records not deleted in the target database that were shared out as deleted. A quick summary of previous table compares that have run will also be available with the table provided in the Previous Table Compare Executions section. 

Additionally, you can run a report with your table compare results. 

Here's how to view your results:

1. Go to Perspectium > Perspectium Core > Tools. Click Table Compare: ServiceNow to Database.
   
   
2. Then, click the table compare that you want to view (either Audit Shares, Compare Records by Table, or Synchronize Deleted Records).
   
   
3. Scroll to the Previous Table Compare Executions table. This table will provide you with a quick summary of previous table compare executions. Click the timestamp in one of the entries to view more information about that specific table compare execution such as the bulk shares or dynamic shares involved, the table and conditions use, the time frame, and the individual discrepancies in the target database. 
   

   When looking at the results, numbers (such as the Records Reshared to Target to indicate discrepancies between ServiceNow and the database that had to be reshared) will have a background color to indicate as follows: 

   Number Background Color	Description
   Green	No (0) discrepancy between ServiceNow and the database
   Yellow	10% or less discrepancy between ServiceNow and the database
   Red	More than 10% discrepancy between ServiceNow and the database

    A Status of Reshared and a Target Discrepancy Type of Not Found indicates the record was not found in the target database and has been reshared. Once the Agent has processed both the reshared message and the compare message to validate the record is in the database, this will update in here to Synced in Database. Note, for each time a record is not found and reshared (even if the same record has to be reshared multiple times because it can't process successfully), a new row will be created in the results with a Status of Reshared and a Target Discrepancy Type of Not Found.

   If using Conditional Shares, the Total Records Compared will be the total of records shared to all conditional shares. For example, if your bulk share has 2 conditional shares and one conditional share shares out 173 records and the other shares out 27 records, the Total Records Compared will show 200 records compared.

   
   

4. (Optional!) If you want to export the results as a .csv or .pdf file, click the available buttons at the bottom of the table. Want to run your own reporting? You can do so by going to the Table Compares (u_psp_table_compares) table. Then, click into the record you want to view.
   
   
5. In Krypton 8.2.0, the table the compare results are for along with the ability to delete the table compare results record (deleting it from the u_psp_table_compares table) was added. Note the table etnry will show as blank if it's not able to find the table the table compare was configured against, such as when the bulk share related to it is deleted.

As of Krypton 8.4.2, previous table compare executions that were run more than 60 days ago will be deleted to improve performance and minimize size on the u_psp_table_compares table.

Performance Statistics 

To give you an idea of the table compare performance, tests were ran on a ServiceNow instance with two nodes, bulk sharing incidents with 4 MultiOutput processors jobs and records that averaged 5 KB in size. The total time for table compare to complete from ServiceNow to a database was as follows: 

↑ Go to top of page

Click to explore the rest of the features available in the Tools module.