> Taskkill will be ok if no one user worked with yours database and no internal
> process worked with your database. And it's not OK when you have more
> than one database on such server, because you interrupt working sessions to
> another databases.
All of which will not corrupt a database if F
Taskkill will be ok if no one user worked with yours database and no
internal process worked with your database. And it's not OK when you
have more than one database on such server, because you interrupt
working sessions to another databases.
I corrupted databases very well with such method. I
> If you execute taskkill /IM fb_inet_server.exe /F then you are kill your
> database(broken indexes, missing data or some else things. if autosweep is
> on, you may completely kill your database).
Not true at all!
We use taskkill all of the time to force a shutdown of FB instances when we
nee
If you execute taskkill /IM fb_inet_server.exe /F then you are kill your
database(broken indexes, missing data or some else things. if autosweep
is on, you may completely kill your database).
If your users is not sysdba or owner of database use shutdown mode, this
method rollback all transaction
What is the best way to disconnect and end all user connections to a FB v2.5
database running in Classic mode on a Windows server?
This will only occur when an update is being applied, so users will have
advanced notice not to be using the database.
I've been told I can just run the taskkill /I
