That may very well be the solution.

Now, the tables I'm dealing with hold more than a million records, and the
application is doing real time (more or less) data capture. Is there a
different way to "touch" the deleted records so they go away?


Regards,


Bill

-----Original Message-----
From: hans@... [mailto:hans@...]
Sent: Thursday, November 01, 2001 6:17 PM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Child Tables Problem Revisited


I think Ann mentioned once, to issue a count(*) once in a while
reclaims the database space.

--------------------------------------------------------------------

Bill Morrison wrote:

>
> Hi Doug,
>
> I've modified it so it is doing the transactions the way you described,
> and I still have the same problem with the database size creeping up. Note
> that it does cause a small performance issue, but once I resolve this

other

> problem I can restore it and see if it's a culprit.
>
> If I watch the allocated pages for the database, it'll increase by 1 or

so

> every 500 records. Only the deletions and additions are occuring.
>
> Regards,
>
> Bill
>
> -----Original Message-----
> From: Doug Chamberlin [mailto:DChamberlin@...]
> Sent: Wednesday, October 31, 2001 7:43 AM
> To: ib-support@yahoogroups.com
> Subject: RE: [ib-support] Child Tables Problem Revisited
>
> At 10/31/2001 10:25 AM (Wednesday), Bill Morrison wrote:
> >I am using the tiCommitted for the isolation level, and explicity

commiting

> >after every 15 writes, or 15 seconds (the system averages 6 written

records

> >/ second). Commit-Retaining is not used. In addition, I have verified

that

> >the OAT is advancing normally. I cannot imagine how I could be any more
> >specific with my transactions.
>
> Sounds to me that you should be committing every time you do the write
> logic. For example,
> 1) Start Trans
> 2) Check for needing to delete existing record and delete it
> 3) Write new record
> 4) Commit
>
> If you did it this way you would be sure the other process would see every
> written record immediately after it was committed.
>
> I'm curious as to why you commit every 15 writes or 15 seconds. Have you
> tried something like I've suggested above and actually observed a
> performance problem with it? That's the only reason I can think of not
> committing every write.
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/