We used the process that Misi outlined and it worked very well. Our installation is enterprise level with over 1000 incidents created daily and we were able to complete the migration with 4 hours of downtime. The actual data migration was less, the rest was coordination between the team members and validation of the migration before releasing the system to the customers.
Jim Coryat Micron Technology Inc. From: Jason Miller [mailto:jason.mil...@gmail.com] Sent: Wednesday, June 13, 2012 12:30 PM Subject: Re: Migration from Solaris/Oracle to Windows/MSSQL ** For the data move there is also Meta-Update. It isn't as free as RRR|Chive but very flexible. If you are moving like for like ITSM version (you didn't mention the versions or if it is even ITSM) then RRR|Chive will do the trick. If you need to massage data, relationships, CMDB classes, roles and permission groups when going from an older version of ITSM to a newer one the Meta-Update maybe worth it. http://www.softwaretoolhouse.com/product/SthMupd/index.html No matter what using a tool that goes through the Remedy api is the way to go. If you did a the conversion at the db level that conversion will always be held in question if problems arise down the road (aka that method is not supported by BMC). Jason On Wed, Jun 13, 2012 at 6:51 AM, Misi Mladoniczky <m...@rrr.se<mailto:m...@rrr.se>> wrote: Hi, Do a fresh install, import the definitions (maybe using Migrator). But use RRR|Chive instead to move the data. It is faster and more robust in this regard, and is designed to handle a high volume of records. Documentation, no login required: https://www.rrr.se/c/doc/rrrchive/?arslist Download and configuration: https://www.rrr.se/cgi/rrrchive/main?arslist Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Hi All, > > We're currently in the process of moving a Solaris/Oracle (11g) based > system to a Windows/MSSQL (2012) environment. While using Migrator should > absolutely work, the fastest way would be to just import the Oracle DB > into the new MSSQL DB and we'd prefer that. The problem here is, that > there are two providers in MSSQL to import data from Oracle databases and > both don't manage to import all data completely and correctly. The ".net > Framework Data Provider for Oracle" doesn't copy views, but manages to > import all data, but the views would be required for the AR server to > function correctly. The "Microsoft OLE DB Provider for Oracle" does copy > views as well, but doesn't set the correct data types when creating tables > and thus fails to import data after some time. > The question is: has anyone performed a migration from Oracle to MSSQL by > just importing the database to the MSSQL server? Or should we just stick > with the Migrator for this matter? > > Regards > Jan Hartung > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > attend wwrug12 www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug12 www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com<http://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"
