You are right in that you can do it all in one job and if this suits your business then this would be the way to go. It's the way that the out-of-the-box rules for BMC discovery tools work.
However, using a staging dataset is still in BMCs best practice recommendations - see the Concepts & Best Practices Guide for CMDB 2.1 Page 87. The paragraph says: "Instead of merging multiple discovery sources directly into your production dataset, merge them into a consolidated discovery dataset first. You can compare this against your production dataset and use the results to generate change requests or exception reports for any discrepancies." For flexibility in the future I would always implement a staging dataset unless there was a compelling reason not to. Cheers Peter > From what I recall from training, that was a best practice before CMDB 2. > They recommended NOT doing that in CMDB 2 training for performance > reasons. > > Otherwise, I'm not sure I see a point in creating separate rules for > determine the best-of-the-best and then having another set of rules for > reconciling into Gold. It keeps track of where it gets each attribute > from, so there's no need to have another reconciliation job to determine > which one is best, because it will simply use the best one as defined by > your precedence rules either way. > > Concerning your last point, perhaps I haven't done enough recon work, but > it seems you're either going to have to add your staging dataset to the > recon rules for your new data source, or you're going to add your Gold > dataset. That seems like a wash either way. Then again, perhaps I'm just > missing something. > > Lyle > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Peter Romain > Sent: Thursday, January 22, 2009 4:19 PM > To: arslist@ARSLIST.ORG > Subject: Re: Reconciliation IDsþ > > BMC best practice is to merge multiple CI sources into a staging dataset > before merging into production. > > This allows you to keep the recon rules creating the best-of-the-best > imported data separate from the business recon rules you use to update > your golden dataset. > > It also makes it easier to add new data sources as you don't need to > include the golden dataset in each of the individual import recon rules. > > Of course, it increases the number of CIs but I think that's a price worth > paying to keep things manageable. > > >> Why are you merging A and B into C and then C into Gold rather than >> merging A and B (and perhaps C depending on whether it has any of its >> own >> data) directly into Gold? Which version of the CMDB are you using? If >> you're on version 2 or higher, it keeps track of which dataset each >> attribute came from, so it still applies all of your precedence rules >> regardless of what order you merge the different datasets into Gold. >> >> Lyle Taylor >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:arsl...@arslist.org] On Behalf Of Heanai >> Sent: Thursday, January 22, 2009 12:39 PM >> To: arslist@ARSLIST.ORG >> Subject: Reconciliation IDsþ >> >> Hello, >> >> I am having a bit of an issue. I have two datasets A and B. I use the >> Reconciliation Engine to merge attributes of these two to C. This works >> fine. However when i try to Reconcile C to the Gold Dataset it doesn't >> work >> as C already has a Reconciliation ID. Is there any way around this? >> >> Thanks, >> Sean >> -- >> View this message in context: >> http://n2.nabble.com/Reconciliation-IDs%E2%80%8F-tp2199691p2199691.html >> Sent from the ARS (Action Request System) mailing list archive at >> Nabble.com. >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" >> >> >> NOTICE: This email message is for the sole use of the intended >> recipient(s) and may contain confidential and privileged information. >> Any >> unauthorized review, use, disclosure or distribution is prohibited. If >> you are not the intended recipient, please contact the sender by reply >> email and destroy all copies of the original message. >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" > > > NOTICE: This email message is for the sole use of the intended > recipient(s) and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. If > you are not the intended recipient, please contact the sender by reply > email and destroy all copies of the original message. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
