Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- From: "Mark J. McGinty" <mmcginty@xxxxxxxxxxxxxxx>
- Date: Mon, 25 Apr 2005 03:33:09 -0700
[snip]
> 4) I was talking about a database with 1 table because I moved this table
> out from the original mdb. but in fact, the mdb database has around 50
> tables. since this mdb database is a front end to an oracle database,
> replacing the mdb access with oracle has a big impact : moving a lot of
> access macros/stored procedures to oracle Pl/sql.
I guess the non-obvious thing, then, is why you're using any Jet tables at
all? Why not leave all the data in Oracle, and process it there? Surely
Oracle is almost infinitely more capable than Jet? (I have no experience
with Oracle, but happen to know first-hand that Jet sucks.)
-Mark
.
- References:
- Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- From: Mark J. McGinty
- Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- From: Mark J. McGinty
- Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- From: Dmitriy Antonov
- Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- Prev by Date: Re: Help on Showing Forms
- Next by Date: RE: Required fields and boolean type in ADO
- Previous by thread: Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- Next by thread: Re: update 500000 records with adodb.recordset resize the mdb from 140M to 2G
- Index(es):
Relevant Pages
|