why duplicate MS SQL Databases/CI's are created in CMDB by the mid server/discovery?

[pavan garige]

There are multiple duplicate MS SQL Databases has been created in CMDB by Discovery.
is IRE does nor cerate duplicate tasks?
Is IRE allows to create multiple duplicate Databases?

#Discovery
#CMDB
#IRE

#duplicate databses

#duplicate Config items

[Amit Gujarathi · Accepted solution]

HI @pavan garige ,
I trust you are doing great.

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.

[Amit Gujarathi · Accepted solution]

HI @pavan garige ,
I trust you are doing great.

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.

[pavan garige · Accepted solution]

HI Amit,

Thanks for your information and quick response.
we have existing configured identification rules for MS SQL Database class and this rule has criterion attributes are 'Class' & 'Data Base' , while doing discovery for MS SQL Databases, many Duplicates MS SQL Databases are created by same name.

Can you help me on this why duplicate MS SQL Databases are created even we have Identification rule for MS SQL Database class.
is there any mistake in the MS SQL Database identification rule(such as any mistake in the criterion attributes) ?

[Canjura]

Hi Pavan, 

Did you ever find the solution to this issue?

I'm having the same issue.

Thank you.

[Ian Roper]

I believe this is by design, check to see if the version is different for each CI.