Service Mapping & Discovery creating Duplicate records in MSSQL Instances

Suvetha S
Tera Contributor

‎03-20-2024 01:59 AM

Hi All,

We noticed few duplicate records in MSSQL Instance table with Discovery source as ServiceWatch and ServiceNow. The record from Discovery schedules has a suffix @MSSQLSERVER and from Service Maps its @MSSQL. ServiceWatch record is missing few important fields like Version, Edition, while we have them from Discovery schedules.  We checked the Service Maps which is using the DBs and found that earlier the CI from Discovery was being used in the map and recently it created a record and it replaces the Discovery record with Service Mapping CI. Has anyone faced this issue? How can we remediate them? Please share your inputs. Thanks. 

0 Helpfuls
  • 702 Views
2 REPLIES 2

AJ-TechTrek
Giga Sage
Giga Sage

‎03-20-2024 06:25 AM

Hi @Suvetha S ,

 

This issue due to IRE rules only, you must check and fix the IRE rules for Database class or MSSQL Instance class.

 

As well as you need to use the Unique value to prevent to create the Duplicate records.

 

  1. Configure IRE to route incoming records based on the uniqueness of certain fields. In this case, we will configure IRE to check the uniqueness of the database records based on essential attributes like database name, server name, and other relevant identifiers.

  2. Duplicate Check: When a new MS SQL database record is created by Discovery, IRE will automatically check if there are any existing records in the CMDB with the same database name and server name combination. If a duplicate entry is found, IRE will take appropriate actions as defined in the routing rules.

  3. Actions on Duplicate: Based on the duplicate check result, IRE can be configured to take different actions: a. If a duplicate database record is found, IRE can reject the creation of the duplicate and send a notification to the relevant IT teams. b. IRE can update the existing duplicate record with the new information from Discovery, keeping the data up-to-date and consistent. c. IRE can close the new record and associate it with the existing duplicate record.

  4. Error Notifications: In case of any errors or exceptions during the duplicate check or record handling process, IRE can be set up to send notifications to the designated IT personnel, providing them with details of the error and any necessary steps to be taken.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

0 Helpfuls

Rahul Priyadars
Giga Sage
Giga Sage

‎03-20-2024 11:31 PM

Few Inputs 

(1) Place a recon rule which will drive the data precedence from Discovery Sources.

(2)  Check IRE rule for CI match for MS SQL Class. If needed add more IRE rule for CI Updates.

 

Regards

RP

0 Helpfuls