At 01:44 PM 16/07/2003 +0100, you wrote:

>Hi,
>
>I have noticed similar behaviour with my applications - although I only
>noticed it when starting to use embedded server.
>
>I was wondering if it may in my case be because the database server(being
>embedded in the application) does not cleanly
>disconnect from/shutdown the database(I currently still have connections
>open when the app exists) and then when next
>starting needs to do some kind of crash recovery ?

Crash recovery - no. It doesn't do it because it doesn't need to.

But - if you are on XP or WinME then the fact that you didn't notice the
effect until using embedded server would be explained by the fact that
SystemRestore does its dirty deed each time the file is opened. Because an
embedded app gets an exclusive lock on the database file, you'll literally
get a SystemRestore every time you open your app.

In normal client/server mode, it's the server that opens the file and gets
the exclusive lock, so it will be the first user to log on who experiences
the delay.

Helen

NB Ryan, since I wasn't sure you actually read down as far as my comment,
I've left it here (below).

-----Original Message-----

>From: Helen Borrie [mailto:helebor@...]
>Sent: 16 July 2003 00:11
>To: Firebird-Java@yahoogroups.com
>Subject: Re: [Firebird-Java] Strange initial startup behavior
>
> >But thats no solution for my Win32-Application-problem :( .
> >
> >Any ideas how 2 avoid this initial startup procedure/file scan ?
>
>Noting the discrepancy between Linux and Windows that you report, my guess
>is that you are using WinXP or WinME and have a database file with a ".gdb"
>extension. If this is the case, try renaming the file with ".fdb"
>extension and see whether it changes the behaviour.
>
>See the Firebird 1.0 release notes for an explanation.
>
>Helen