--- In firebird-support@yahoogroups.com, "rajsubramani"
<rajsubramani@y...> wrote:

> Most other DB's I work with have a concept of DB owner which
> goes with the DB file(s).
> By delegating user password security to security.fdb
> hasn't this been circumvented?

I know not one decent DBMS which does have this concept. At least no
server based DBMS.

> Hey presto, the third party can now set SYSDBA and password to his
> choice, connect to my DB, drop the triggers or whatever.

As soon as you give the user physical access to a file he can screw
things up. If they delete the whole file, the application would not
work as well, right? So where is the difference to dropping the trigger?

The DBA of any database installation will always be able to access the
data. There is no way around that (just like your network
administrator will always be able to read your emails or the contents
of any file on your harddisk)

Thomas