Skip to main content
Solved

Migrating Access Database to Oracle

  • November 23, 2015
  • 2 replies
  • 11 views

Forum|alt.badge.img+1
Hi,

 

 

I have an Microsoft Access 2002 database with a number of look up tables and was wondering how I would go about migrating this to Oracle using FME 2015 while keeping the relationships between the main table and the look up tables.

 

 

Thanks

 

Best answer by david_r

Hi

 

 

The simplest solution is to use the functionality in File / New / Generate workspace to set up the workspace for you.

 

 

FME is amazing at translating data, but translating relations etc. isn't its strong suit, so you'll mostly have to define the foreign keys, indexes etc. manually in Oracle. You can use something like Toad or SQLDeveloper for this, they make it fairly easy to do in a user-friendly interface.

 

 

David

 

View original
Did this help you find an answer to your question?
<strong>This post is closed to further activity.</strong><br /> It may be a question with a best answer, an implemented idea, or just a post needing no comment.<br /> If you have a follow-up or related question, please <a href="https://community.safe.com/topic/new">post a new question or idea</a>.<br /> If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

david_r
Celebrity
  • Best Answer
  • November 23, 2015
Hi

 

 

The simplest solution is to use the functionality in File / New / Generate workspace to set up the workspace for you.

 

 

FME is amazing at translating data, but translating relations etc. isn't its strong suit, so you'll mostly have to define the foreign keys, indexes etc. manually in Oracle. You can use something like Toad or SQLDeveloper for this, they make it fairly easy to do in a user-friendly interface.

 

 

David

 


takashi
Influencer
  • November 24, 2015
Hi,

 

 

Agree that using a tool like SQL Developer is easier way, but if you are familiar with SQL syntax, you can also add required constraints (foreign keys etc.) to the destination database by setting the SQL statements directly into the "SQL Statement To Execute After Translation" parameter of the writer.

 

 

Takashi

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings