- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2018 07:22 AM
Hello, We are facing an issue with duplicate instance records within the MSSQL server instance records. We've recently started development on MSSQL Discovery to populate some additional information and to get AG, mirroring databases, clusters etc. For that, we've built a new probe and sensor with the help of Powershell script from DBA team and disabled the out of the box probe, sensor and classifier. Everything is working as expected like creating an instance with all the desired data, related catalogs and etc. But, here is an issue coming up with inserting records on CMDB. We already have some existing instance records in the CMDB instance table, when we run the Discovery, in some cases it creates a new empty record just with the instance name instead of updating the older one. In some case it updates the old one but creates the new record. In some cases if there multiple records for the same instance it either updates one record or doesn't updates both records, creates new record with updated information. We've also created a Business rule to update the older record if it finds the existing record with the same instance name else to create a new record. It worked in the beginning but when we started to test different servers it was still creating duplicates. can anyone help me with the troubleshooting to solve this issue. Thank you!
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2018 10:39 PM
Hi Rakeshunu,
You can create a separate identifier for MSSQL instance like below. This would avoid creating duplicated entries
Regards,
Vivek
Based on the impact hit like helpful or correct

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2018 10:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2018 04:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2018 08:00 PM
Vivek, I know creating Business Rule in regards of Discovery to stop duplication is not the best practice. I was expecting an answer from you right after I posted this question, I've seen many questions solved by you on Discovery.Please help me on this, it's being a huge issue from long time. Please help me with solution. Above solution is not working. Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2018 10:57 PM
Thanks Rakesh
In the identifier rule, Instead of "Instance name" in criterion attributes add the field "Name". Some companies do not follow a unique name for DB instances so that might create duplicates. Discovery will create Name field as InstanceName@Servername. so if your server names are unique then your DB instance "Name" field also will come as unique. So I guess changing the criteria as "Name" field would work in your case.
Let me know if this works.
Regards,
Vivek