Access to Oracle

[yippie_ky_yay]

Hello everyone,

I was reading some job postings (trying to figure out what skills I should get) and a couple of the terms used are throwing me off.

For example: "performing migrations from Access 97 to an Oracle platform"
Is "migration" just another way to say "exporting tables"?

I have worked with both Oracle (8) and Access before. What kinds of things should I keep in mind if I had to perform this function? Other than making sure the field names are correct (no spaces) - I don't see much that I would have to watch for (ie I'm pretty sure that there wouldn't be any size restriction issues).

As usual, any info is welcome!

-Sean

 

[WayneRyan]

Sean,

Migrating entails moving the application from one
platform to another. There are several issues
involved:

1) Data Migration
2) Redevelopment of Forms/Reports (can not reuse
any of your Access components.
3) Security will have to be redone. ORACLE supports
users/roles (similar, but different).
4) Different concepts to support; ORACLE has table
constraints and table triggers.
5) DBA requirements. Maintaining tablespaces etc.
in ORACLE.

There are many aspects to the migration where a
component is supported by both environments, but
you can't use your prior building blocks.

Just some quick thoughts, it'll be interesting to
see where this thread goes.

Wayne

 

[yippie_ky_yay]

Hey Wayne,

sounds like you know about this!

When it says "performs migrations", I thought that it meant either exporting the tables or just updating an Oracle db from an Access one. Wouldn't that be the case if the Oracle db was already set up and working properly (with triggers set, security in place, etc... ?).

Thanks!
-Sean

***edited***
just looked up the term "migration" on webopedia - it means to completely change over. I thought that that might be what it is, but I can't imagine performing db migrations to be a major job function. Sounds like they have to do one and they just want to make sure that they got someone who's done it before!

 

[SteveA]

While our area uses SQL Server instead of Oracle, we have dedicated teams that are continuously undertaking the process of migrating Access based databases to SQL Server.

This process includes the creation of the SQL Server database and associated settings as well as the creation of an enterprise based front-end (automatic deployment or intranet (html/asp)).

It is a full time job for several staff across multiple areas of the organisation. We currently have a project operating that is converting 12 seperate Access databases across to SQL Server and VB.

I can't see the work load running out any time soon.

Cheers
SteveA

 

[RichMorrison]

Sean,

You wrote
<<
When it says "performs migrations", I thought that it meant either exporting the tables or just updating an Oracle db from an Access one. Wouldn't that be the case if the Oracle db was already set up and working properly (with triggers set, security in place, etc... ?).
>>

That is what I think it means. If one uses Oracle software tools to create screens, reports, etc, then it sound like "conversion" to me.

I have made serveral apps with Access 97/2K that use Oracle tables as a data source. These apps also use local Access tables so it is a "2-tier" approach.

In general, I talk with Oracle DBA people and they create tables, triggers, stored procudures, etc. Then I make the front end to manipulate Oracle data.

So far it has worked well.

RichM

 

[yippie_ky_yay]

Thanks guys - some interesting feedback to think about!

I've been playing with the trial version of SQL Server over the past couple of days (re-creating micro versions of what you both described) to try to get a better understanding for all this (I chose SQL Server and Access because I figured two MS products would be the easiest to "migrate").

So far so good - but some of the features are a little trickier than expected. I thought it would be worth suggesting because soon the mere mention of servers or any server terminology will no longer leave me feeling so unsure.

-Sean