Yep, if there is no commit for each record it sure aint a sweep
kicking in. The only time I've found the server to mercilessly hog
all CPU is during a sweep, is all. I'll be moving to Win2000 soon.
Will be interesting to see if I hit the same issues others are
reporting with that OS.

Regards,
Andrew Ferguson
-- Where every day is Opposite Day.

--- In ib-support@y..., "Adrian Roman" <aroman@r...> wrote:
> Hi,
>
> I cannot hit a sweep, since I just created the database, imported
the table
> (30000 records), and did
> update "table_name" set "field_name"='666';
> first time it went in a couple of seconds. Without commiting the
> transaction, the second time went for 10 minutes.
> I guess I didn't hit the limit for a sweep, since it takes 20000
> transactions for a sweep to start. And that's only if 20000 is
between OIT
> and the current one, which is really not the case, since importing
was
> commited, and there is only one transaction active... Anyhow, I
tried with
> sweep interval set to 0, with the same result.
>
> Database header page information:
> Flags 0
> Checksum 12345
> Generation 27
> Page size 8192
> ODS version 10.0
> Oldest transaction 20
> Oldest active 21
> Oldest snapshot 18
> Next transaction 23
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 0
> Implementation ID 16
> Shadow count 0
> Page buffers 4096
> Next header page 0
> Database dialect 3
> Creation date Jul 13, 2002 13:07:58
> Attributes
>
>
>
> Adrian Roman