>From BMC R&D: "Yes, I just received something from R&D that appears to be procedures to delete orphan records. However, it still appears to a manual effort."
Ramon, If you know of another workaround please advise. Thanks, Brandi Barbour Sr. Software Engineer Development Services [email protected] <mailto:[email protected]> T 972-431-2944 From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mark L Sent: Tuesday, June 12, 2012 12:08 PM To: [email protected] Subject: Re: FW: WARNING: 7.6.X DDM AND ITSM ** I'm curious how many people wouldn't require a solution to this gap if they were going to use DDM. Wouldn't not accounting for hard deletes be a big risk to data quality post-migration? Cheers, Mark From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patrick zandi Sent: Tuesday, June 12, 2012 10:38 AM To: [email protected] Subject: Re: WARNING: 7.6.X DDM AND ITSM ** This by far is the best answer I have seen in a while (excluding david ) and how encouraging it is to see someone say, "We acknowledge" and "we are working on it" and "We thank you for your feedback".. WOW , Really nice... I am encouraged. Those 3 things are encouraging.. On Tue, Jun 12, 2012 at 10:25 AM, Kagan, Ramon <[email protected]> wrote: ** HI, We acknowledge that hard deletion of records is not something that is currently designed for with the DDM tool. The general consideration on this was due to the fact that "soft" deletion is the prolific model officially designed for in the applications. While hard deletes are possible, they often require both administrative access as well as taking the two step process. We have heard from customers (and not all) that they are conducting hard deletes and we are working to close this gap in a future release. If you are in a situation where you require a solution to this gap, please contact BMC Customer Support and an interim solution can be provided. We thank you for your feedback, it is always appreciated. ________________________________ Ramon Kagan BMC Software From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Goodall, Andrew C Sent: May-03-12 12:26 PM To: [email protected] Subject: Re: WARNING: 7.6.X DDM AND ITSM ** What makes me laugh is that this is BMC's official product to primarily migrate their ITSM customers from previous versions to the latest and "greatest". Yet they don't cover all the aspects for their own product ITSM. Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com <http://www.jcp.com/> From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Guillaume Rheault Sent: Thursday, May 03, 2012 11:10 AM To: [email protected] Subject: Re: WARNING: 7.6.X DDM AND ITSM ** That's the reason why you need to use RRR|Chive, which is THE tool for data migration. DDM is not production ready yet, it's a nice concept but very limited. With all the money and resources that BMC spent on DDM,they could have just paid Misi from RRR to make RRR|Chive "prettier", i.e. essentially having a GUI and colorful reports so management **thinks** it's enterprise ready. You know how it is, management needs to see pretty power point slides to think (when they think) that a tool is enterprise ready. RRR|Chive does not have that prettiness,thanks God, but get's the work done. It's probably because Misi focused on the design of the tool that it works, instead of focusing on sugar-coated prettiness and fluff, which takes the focus away in developing something that really works. Guillaume ________________________________ From: Action Request System discussion list(ARSList) [[email protected]] on behalf of Goodall, Andrew C [[email protected]] Sent: Thursday, May 03, 2012 11:54 AM To: [email protected] Subject: WARNING: 7.6.X DDM AND ITSM ** This is a heads up to anyone planning a 7.6.04 upgrade. So we're using DDM (Delta Data Migration) to migrate data to the new 7.6.04 environment from our existing 7.5 implementation. Well DDM is migrator based and it does not keep track of DELETE operations. ITSM workflow will often use DELETE operations on foundation data such as people permission, support group and functional role removals, product alias changes, etc... So now we have to keep track of all these changes and manually remediate them. As you can guess in a large enterprise this is substantial. Thank you BMC, thank you very much! Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com <http://www.jcp.com/> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer. _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ -- Patrick Zandi _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com <http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
