Legacy Sybase Data Migration
Sorry, I've been a bit slow getting posting up recently. Finally the book is done. My last blog I announced the publication, but there was still a lot of last minute crunch time editing. Happy to say that the ink is wet, but will be dry by Open World. You will be able to grab a copy at the book store there, or from all the good online bookstores. (amazon.com uk, dk, de, fr...etc for you amex users) http://www.packtpub.com/oracle-modernization-solutions/book
Anyway...done plugging.
So, getting a lot of Sybase migration questions these days. There are a couple of ways that we can look at doing this, and it depends on what the requirements are, of course.
You can use SQL Developer and use some of the updated technology we had from the migration workbench to port that code over. That is the 'cheapest' way to do this. It can parse and and understand the Stored Procs much better than it used to.
Some of the customers have an issue of the actual time it will take to do the port..aka, the batch window from switching one db off, so the migration and sql loader path won't work because the database is just too large and there is only a few hours to port it over.
This is when we start looking at some of our partners and leverage some cool replication technologies. Yikes running out of time. Let me give you some of those details in the next installment....this week I promise
