Import from one table to another

FLabrecque

Registered User.
Local time
Today, 10:43
Joined
Nov 9, 2004
Messages
93
I wish to use one of my database (call it DB #A) to import ODBC tables into a second database (DB #B). From what I figure, I can't directly import into another DB. I'll have to use these steps:

1. Delete Link in #A that points to #B.Table.
2. Import table in #A.
3. Delete Table in #B.
4. Export table in #A to #B.
5. Delete Table in #A.
6. Create a link in #A that points in #B.

Is there any simpler ways to do this? I would really enjoy discovering a way to directly import in #B. Otherwise, #A gets a lot of bloat (especially since I need to import on a daily basis 6 tables of 60,000-100,000 records)
 
Join your tables appropriate in a query, then delete the records returned.

You'll have multiple such queries.
 
You suggest that I have a dummy table in DB #B, and use an insert to populate it, with an SELECT statement to my ODBC table.

This would be fine if my table was from Oracle, MySQL or other more "standard" sources. It comes from a mainframe. The way it is set, I can't link to it's data (or risk loosing the link in the process). It would be fun to ask the mainframe guys to change it, but that's not an option.

Other suggestions?

By the way, I do appreciate your help! :)

EDIT: I should state that this argument doesn't come from me, but from the mainframe usage policy, saying "can't link tables".
 
Last edited:
then its not really a table link problem is it?? its more of a export/import excerise, in which case its just a case of getting the mainframe data out (connectdirect or whatever) and then importing it into the db.
 
It never was a link problem. The only link I talked about, was between DB #A & DB #B. Perhaps I wasn't clear. The imported table comes from Source #C.
 
First, it's company policy to not link on the mainframe. It's not my decision, and I'm not here to defend that (as pointed before). And no, I can't get to change their minds.

My initial question was if there was an easier way to do this, which meant importing directly into another DB (or in this case, several other DBs).

I've coded my initial process. Which works, but I have a lot of bloat created that I'll need to purge often. Thank you for your response.
 

Users who are viewing this thread

Back
Top Bottom