Re: OleDb delays commits and unlocks?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I accept that rebuke; your assessment may be true, but I have
left significant complexity out of this discussion because of its
tendency to hide the real problem that I am fighting. (Case in
point: the table names and column names are not the same
between the files.)

Yesterday, we "stumbled" onto evidence that convinces me my
two problems are just different manifestations of the same i
ssue: the lazy write characteristic of the JET engine. If I can turn
that off while this process runs, both problems will go away. I
can find VB examples of ways to do it, but they don't seem to have
C# counterparts in the OleDb family of classes. The
JRO.JetEngineClass.ResetCache() method is available for
refreshing the read cache, but doesn't have an equivalent for the
write cache--which would also solve my problem. Got any
suggestions on this?

"Cor Ligthert[MVP]" wrote:

John,

From your description I was not sure if you had to update datarows or only
to insert.
As you state it now probably a simple merge can do the job (as long as you
use the same tablenames and the same columnnames).

Why avoid simple tools for simple jobs.

Like you write it, it seems to me that you want to use simple tools for
difficult problems and more basic tools for difficult jobs, as I try to say
it in an anology.

It looks that you are using a stappler to build a house and a hammer with
nails to put some papers together.

Cor

"John W." <JohnW@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:21CBB04B-1050-4167-BCED-4868EE839454@xxxxxxxxxxxxxxxx
I avoided using DataAdapters since (1) the operations I needed were so
basic,
(2) I don't feel very comfortable with them, and (3) with the exception of
two tables, I don't need to have the updated tables in memory--only in the
file. (Those two tables are used to reconcile several foreign key columns
in
various tables.) CommandBuilder lost favor with me a long time ago when I
found that it couldn't handle half of what I wanted it to do. (I don't
remember the specifics, but I do remember the disappointment.) The two
tables
in Problem 2 should be among the simplest to handle. One of the new
records
is always the same, and the other varies only slightly. Two INSERT
commands
and I'm done, without the overhead of the DataAdapter.


.

Relevant Pages

  • Re: Newbie tool set advice
    ... What basic tools do I need? ... sockets & spanners come to mind. ... tools be OK for may jobs? ... First priority, as you have realised, are spanners and a decent socket set. ...
    (uk.rec.cars.maintenance)
  • Re: Jobless rate highest since Carter... 10.7%
    ... Instead it created around 22 thousand jobs. ... The democrat/republican false paradigm is to divide the country against ... you have to get into the faces of your local politicians and tell them that you do not support their ideology. ... The real problem is the left/right false paradigm that people think is real. ...
    (comp.sys.mac.advocacy)
  • Re: Survey: CAD Posts.
    ... It forces management to evaluate every employee's value. ... The meeting then goes on for 4 more hours trying to get him onboard, ... into three large jobs this year where we got absolutely killed. ... Of course he isn't the real problem. ...
    (alt.machines.cnc)
  • Re: nbc Only in America nbc
    ... hire illegals and enforce those penalties. ... Take away the jobs and the illegals will go home. ... the real problem is all the manufacturing companies who moved the good jobs Americans DO want, ...
    (rec.music.artists.springsteen)
  • Re: TCO and users/box
    ... the real problem isn't that the jobs are run in ... it's that multiple users leave the jobs ... unterminated after the jobs are finished, so the memory is never freed, ... until I start seeing available swap start decreasing dangerously and badger ...
    (comp.os.linux.hardware)