• Check for errors under SysJobHistory in msdb by running:
  
  SELECT * FROM msdb.dbo.sysjobhistory WHERE sql_severity > 0 order by run_date desc, run_time desc
  
  Expand the step_name and message column to see the details against latest job run date and time. TIP: Read the entries from the bottom upwards because there might be some errors occurring as a results of very first error.  
  
   
  
• Another way to check for an error in any step is to double click on "Job Activity Monitor" and see which step failed with red X marker beside the step name.
  
  There will be at least 2 errors, one failing with main update date job, which will not give information about the exact error/step. However, look for the 2nd error in the job list (DataFlow) to see which step failed.
  
  You can also check how the DUJ has been running historically by running the sql statement :

• Check the tblErrorlog table for any reported errors - be careful to consider the date column as the table it may span several years:
  
  select * from SnowLicenseManager.dbo.tblErrorLog order by LogDate desc
  
  
•  Check for details regarding which step(s) failed by running : 

select * from SnowLicenseManager.dbo.tblJobLog

• Check how the site is configured:

select * from SnowLicenseManager.inv.tblSite

• Check the configuration of Inventory Database(s):
  
  select * from SnowLicenseManager.dbo.tblInventoryDatabase

• In the SnowInventory database there is a schema added i.e. slm. 
  
  All the stored procedures in  the SnowInventory database starting with slm.Get.... are used to load the the data from SnowInventory into "staging" tables in SLM during the first step of the DUJ (GetInventoryData).
  
  These staging tables will be used for the rest of the processing steps. The staging tables will be truncated upon every DUJ run. 
  
    
  
  
• Clients from the SnowInventory database are mapped against each Computer in SLM (one-to-one relationship) in the mapping table in the SLM database  SnowLicenseManager.inv.tblComputerInvSlmMap.
  
  Each client is mapped against each Computer and CID in SLM.
  
  If you see an 0 value in CID and ComputerID column, that means the computer was deleted from SLM.  The deleted computer will no longer transfer over to SLM until it is deleted from SnowInventory and reports in again with a new clientId.

•  Users from the SnowInventory database are mapped in the mapping table SnowLicenseManager.inv.tblUserInvSlmMap and this serves the same purpose as computer mapping.