Do not had uniqueness on any of the CMDB fields because this will create issues post reconciliation. As you know that Reconciliation does an Identify and merge , so your Source dataset CI gets reconciles into target Dataset which is always Asset then it will have issues for Unique fields. I hope this clarifies, so I would recommend not to add Unique Index on any out of the box fields as well as custom fields. What is the use case behind making it Unique ?
-Thanks Yogesh -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Sweety Sent: Wednesday, March 26, 2014 3:36 AM To: [email protected] Subject: Strcturing CMDB data Hi Experts, Is there any document which specifies each class of CMDB there must be some fields which needs to be unique? I am planning to make 'Name' field as unique for all my CIs in my organization, do you see any challenges here? Please share how you structured your CMDB data in your organization? I am not able to find much help to maintain unique CIs in my organization. Kindly share your ideas _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
