> But from security POV all this is useless as well. Yes, SYSDBA can't
> access this database anymore, but it will take a couple of minutes to
> find out name of "Your user" and a minute later I will be logged in as
> this user with full destructive power.
> On the other hand, if I wish to destroy your data, I can save these
> minutes and simply delete database file as whole.
> As I already said - security battle is lost as soon as enemy has got
> access to server. There is no DBMS which can survive after that.
>
> SY, SD.
>

Our user is not owner of database objects, it's SYSDBA, so if logged in as this user You can delete records, not drop tables.

But it's true, if You have full access to database file, our security rules are ineffective.

Maybe you can add as much as possible count of users in security2.fdb so it will slowdown the thief of Your database (to found the right one) :-)