Subject | Re: [IBO] Freeing connection very slow |
---|---|
Author | Frank Ingermann |
Post date | 2003-07-09T20:34:47Z |
Hi Luke,
tigaris wrote:
What is the extension of your database file?
if it's ".gdb", then it's very likely you've been
hit by a new "feature" of Windows XP - can't remember
its exact name in English (i have a German XP version),
"AutoRestore" iirc.
Look in your windows folder, there's a subfolder
"Restore" that contains a hidden file called
"filelist.xml". That one cannot be changed, and
it contains "GDB" as one of the file extensions
that should be saved whenever such a file changes (!).
The immediate result for GDB's: when the last user
disconnects, the timestamp of the GDB changes, and
Windows is so "kind" as to automatically copy the
entire database file... every time...
Solutions: either turn of the AutoRestore (or whatever
it's called) feature for the drive in question or -
better - name your database file "<name>.fdb" and
avoid the gdb extension.
hth,
Frank
tigaris wrote:
> I moved to a new computer this weekend, upgrading from Windows 2000just to add one to Helen's list of things to check:
> to Windows XP Professional. Now when I free an TIB_Connection
> object in my server code, it is taking an unusually long time to
> disconnect from the Firebird database (like 10 seconds). I am
> running version "WI-V6.2.794 Firebird 1.0".
What is the extension of your database file?
if it's ".gdb", then it's very likely you've been
hit by a new "feature" of Windows XP - can't remember
its exact name in English (i have a German XP version),
"AutoRestore" iirc.
Look in your windows folder, there's a subfolder
"Restore" that contains a hidden file called
"filelist.xml". That one cannot be changed, and
it contains "GDB" as one of the file extensions
that should be saved whenever such a file changes (!).
The immediate result for GDB's: when the last user
disconnects, the timestamp of the GDB changes, and
Windows is so "kind" as to automatically copy the
entire database file... every time...
Solutions: either turn of the AutoRestore (or whatever
it's called) feature for the drive in question or -
better - name your database file "<name>.fdb" and
avoid the gdb extension.
hth,
Frank