Subject RE: [firebird-support] FB GBK and CPU Usage
Author Andrew Stuart
Hi



Whats the quickest way to reset the difference, ie correct it, as a one
off for the time being?



Restart FB service and Sweep ?



Need minimum downtime



Cheers

Andrew



From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Thomas
Steinmaurer
Sent: 13 October 2008 12:28
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] FB GBK and CPU Usage



> Thanks all so far, we're lookin at running with -g during the day and
a
> garbage enabled one at midnight
>
>
>
> However talking to our developer he's not convinced hes' using
> transactions?

I'm afraid, I can of worm then, because the access components are
therefore responsible for doing the transaction stuff, thus leading to
problems like using CommitRetaining when using some kind of AutoCommit.

It's very important to understand Firebird transactions and how to use
them with the access components correctly.

--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/



Head and Registered Office:
Call Assist Ltd,
Axis Court, North Station Road,
Colchester, Essex.
CO1 1UX
Telephone +44 (0)1206 771771
Fax +44 (0)1206 364268

Registered in England and Wales.
Registered Company Number 3668383
Authorised and regulated by the Financial Services Authority

Please Note : This electronic message contains information from Call Assist Ltd which may be privileged or confidential.
The information is intended for the use of the individual(s) named above. If you are not the intended recipient be aware
that any disclosure, copying, distribution or use of the contents of this information is prohibited.
If you are not the intended recipient please delete this email. If you have received this electronic
message in error, please notify us by telephone or email immediately.

Please consider the environment before printing this email.


[Non-text portions of this message have been removed]