>From my original post "I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows."
Even if we were on oracle, the impdp/expdp commands in oracle would overright our current production system when importing. We have an operating production system with production users. ________________________________ From: Joe Martin D'Souza <jdso...@shyle.net> To: arslist@ARSLIST.ORG Sent: Sat, February 26, 2011 11:06:40 AM Subject: Re: CMDB dev to production ** If you are on Oracle, you could use the Oracle imp and exp tools to selectively export and import data. This should work even given the unique nature of relationships in CMDB since you say that your production environment matches your development environment. You may need to manually set your next ID’s if you choose this method. Joe From: John Doe Sent: Saturday, February 26, 2011 11:46 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: CMDB dev to production ** Hi all, I am in the process of trying to figure out how to migrate the CI's in our dev CMDB to production. We have appoximately 100,000. Our production CMDB is an exact copy of our dev CMDB minus our actual CI's. We are just trying to migrate all of our CI's from the dev CDM to the production CDM. I have given thought to AIE (using it to connect to an external database) or using BMC Migrator. Essentially, we would be transferring CI's from one 7.6 remedy system(dev) to another like remedy 7.6 system(prod). SQL Server 08 on Windows. We are currently utilizing other modules in production system with active users. Any ideas? Thank you_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
