Hello. I wrote about databases that became broken for some time ago, for today I do big work for fixing this, but sometimes databases became broken without any reasons.

1. I turn of autosweep

2. I create new firebird user for my application, so that user can't modifi any metadata

3. I became database shutdown so only one sysdba user can change metadata dureing update

4. I create procedure of update when users chuck out from program during process, so only one user connect to database in this time

But there are some problems during all this processes:

1. Sometimes without any reasons if I send database to shutdown mode, it's not happened without killing all processes of fb_inet_server.exe(I hope it's ok, because no one use database in this moment)

2. I use IBExpert for work with db manualy and sometimes somebody forgot to close thit application so I'll try to kill it, but sometimes it's not happened(I don't know why but, I see it)

3. There are problems with servers where there is therminal windwos sessions, sometimes applications don't react for my commands because user close session, but not close applications, so aplication don't closed and windows kept it for fastest enter user in terminal. I kill this applications for the first, If I don't do it I can't kill some connections(it seems to me its bug in windows)

For the last two days I get information about 2 databases that became broken, but the operating system start and shutdown normaly.

Help me please what I doing wrong and what I can do for more no-failture work?