Announcement

Collapse
No announcement yet.

Converting from Oracle to MS SQL

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Converting from Oracle to MS SQL

    Have anybody successfully converted a SM 9.3x from Oracle to MS SQL database on an AIX system?
    Best regards Tommy

    Please do NOT send me private messages asking for help with specific topics. I do not have the time. Post your question in the forums.

    Blog - - ITIL certified - HP Accredited Integration Specialist Service Manager v9

    ServiceNow Certified System Administrator - ServiceNow Certified Implementation Specialist - ServiceNow Certified Application Developer

    Want to keep this site alive? Consider making a donation. Click here.

  • #2
    Haven't ever tried this, but here's a few thoughts that you've probably already come up with

    If it has a small-ish volume ticket-wise, you could do system_unload/system_load (I'm assuming that still works in 9.3x). If it's bigger, take a copy of prod, purge the ticket tables, then do system_unload/system_load to get structure/code and use some kind of ETL to migrate the ticket data.

    Comment


    • #3
      Unfortunately none of those options would be possible.

      The system is huge and I have tried a system unload / load 3-4 years ago (and it has only grown since) and back then the load took more than 48 hours on an 8 core 16 GB pc (oracle db).

      Just a few numbers to indicate size: 1 million+ interactions, almost 1 million incidents. 10 million contacts, 10 million locations.
      Best regards Tommy

      Please do NOT send me private messages asking for help with specific topics. I do not have the time. Post your question in the forums.

      Blog - - ITIL certified - HP Accredited Integration Specialist Service Manager v9

      ServiceNow Certified System Administrator - ServiceNow Certified Implementation Specialist - ServiceNow Certified Application Developer

      Want to keep this site alive? Consider making a donation. Click here.

      Comment


      • #4
        That's where I was getting into the second thought. Get a copy of prod (restore into a test Oracle DB), purge the big tables, then use system_unload/system_load to get a "shell" of the system into MSSQL. Once it's setup in SQL, then use ETL of some kind (eg MSSQL's DTS) to copy the big tables.

        We did something similar last year, but not involving the Oracle->SQL conversion. Ours was from an older version of Oracle to a newer version on new hardware and included an SM upgrade. We started with a backup, purged it out, upgraded SM, got that all up on the new hardware, then used some ETL code in Oracle to migrate the data from old to new. That allowed us to keep downtime to a minimum.

        Comment

        Working...
        X