Ok, this is one way of doing it. I was trying to avoid this method if possible to prevent from reduplicating the data again into datasetC which will eventually impact the BMC_BaseElement query performance if the CI count is huge. Else instead of having two datasets A,B , I could directly bring the data from both the sources into dataset A, that way I can prevent recopying into another dataset.
On Friday, August 16, 2013 10:27:23 AM UTC-7, Tauf wrote: > > Easiest way to think about relationships is to think about them as CI's > also. > The cleanest thing for you to do would be to push the data from > Dataset A and B into a new Dataset C. From there, create your > relationships and then reconcile it into your prod Dataset. > > Sent from my iPhone > > On Aug 16, 2013, at 1:22 PM, patchsk <[email protected] <javascript:>> > wrote: > > > ** > > I have data coming from two different data sources for different CI > Types. > > (Ex: Computersystems in DataSet A, > > IPAddresses in DataSetB). > > So I need to create relationships between them and eventually reconcile > them into production dataset. > > > > No issues with CIs because they can be in different datasets and we can > have different reconciliation jobs to push them to production dataset. > > How to handle relationships in this case. Is it allowed to > > a) Create relationships between CIs in different datasets. > > b) Does reconciliation engine/jobs support reconciling relationships of > CIs belonging to different datasets? > > _ARSlist: "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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
