10-28-2012 07:29 PM
We are currently in the process of planning a migration from TRIM Upgrade 188.8.131.520 on Oracle 10g to 7.x on SQL 2008 R2. Research to date (and some discussions with various vendors) suggest that the easiest way to undertake this upgrade is to change the RDBMS to SQL 2008 R2 with the current version of TRIM and then follow that up with a straight TRIM 184.108.40.2060 -> TRIM 7.x migration.
My understanding is that the TES migration option under tools should be sufficient to migrate existing datasets from one RDBMS to a new platform; provided that the intial database can be confirmed as clean, and perhaps a schema repair on the destination server performed afterwards. Once this has been successfully accomplished, a TRIM 220.127.116.110 upgrade to 7.x using the fresh SQL database should (I assume) be relatively straightforward.
I'd appreciate any thoughts on the above strategy, whether this is the "preferred" methodology to perform a combined TRIM/RDBMS ugprade and/or suggestions on better alternatives.
Please note that the above is just a summary of what is being considered; I'm just interested in thoughts on the overall process. Whatever course of action is ultimately decided upon, I envisage several months of work in DEV and TEST to iron out the exact steps required to safely carry out this upgrade.
Thanks for your time,
Solved! Go to Solution.
10-29-2012 06:45 PM
Your steps are correct, you can migrate using the TES to move from Oracle > SQL.
You can do this either in 6.2.4 or 7.X.
Another customer I have just been working with went from 6.1.3 Oracle 10G to 7.1.2 SQL 2008 a few weeks ago.
They have managed to get there successfully and didn't require too much prior testing/planning to do this.
(They were going to go to 7.1 with Oracle 10G, but it's not supported, so the decision to go to SQL Server was only made fortnight before the upgrade!)
As I advised these guys, run some migration testing now so you understand the process and you can then check to see if your data migrates cleanly and if any errors come up.
NOT A HP EMPLOYEE
Now working for a TRIM consultancy
10-30-2012 12:40 AM
Migrating through TES takes quite a while if you have a large database.
For a ~50GB Oracle database I've once experimented migrating through the SQL Server Data Transformation Services (now replaced by Integration Services) and TES in parallel. By the time DTS was finished (it took just a few hours), TES hadn't even finished exporting TSACCESSCO which was already taking ~20GB of XML files. So if testing shows you cannot finnish in a weekend using TES due to time constraints, then using the database tools is also an option.
But as always, you should test the procedure thouroughly.
HP Information Management & Analytics
Enterprise Information Management
12-03-2012 07:33 PM
Our TRIM database size is roughly 20Gb. As part of a trial test of the data migration process we:
1. Used a 3rd party data migration tool to transfer the oracle data to SQL (excluding all the temp tables etc.)
2. Did a schema repair.
End result was most satisfactory and took about 17 hours to complete on Test hardware.
Note: We did shy away from both TES and SSIS as some individuals advised that both can be time consuming (and in SSIS case, overly complex).
Thanks for all your feedback; it is greatly appreciated.