Create table vs Insert into... (1 Viewer)

[Newman]

Which of these methods do you think is best and why?

1:
-A delete query of the datas of TableX(Back-end).
-An insert query of QueryX to TableX.
-An insert query of QueryY to TableX.

2:
-An union query(QueryZ) of QueryX & QueryY.
-A create table query of the TableX(Front-End) based on QueryZ.

Queries X & Y are long to execute and TableX doesn't need to be live.
I already have a script that does some tasks on that database at night.
I only have to add one task to it.
Should it be #1 or #2?

If you got any other idea, please let me know.
Thanks!

 

[WayneRyan]

Newman,

If the amounts of data involved are really that big, then the
time to make/empty the table is negligible. I'd vote to simply
delete the old data.

I'd think that for populating the data, just throw QueryX at it,
then QueryY. The table just wants the data, there shouldn't be
any need to complicate (lengthen) things with a Union query. I
don't even think Access handles them well.

Method 1 gets my vote.

How much time does the process take? Are you just tossing out
and re-writing 90% of your data? That may be the place to look
if you want to streamline the process.

Wayne

 

[Newman]

I have many queries like these. Many uses Oracle tables with over 1Million records. I use passthru queries as much as I can, but it still takes minutes to load a form.

I do rewrite 90% of the datas, but adding to the fact that I add new records and delete some old ones, I do update some others. So, deleting old ones, updating remaining ones and adding new ones seemed to be a bad way to do it.

I take note of your vote. I do like the first one too, since it doesn't create tables in the front-end.

Thanks for your comments.