> Objects inside the database can be owned by yet
> > other users if you wish.
> > But at all times, SYSDBA will be able to access all objects, backup and
> > restore the database. The owner will also be able to backup and
> restore its
> > database but this non-SYSDBA identity will not be able to
> backup a database
> > for which it is not the owner.
>
> And - I just read in TFB that SYSDBA is created upon installation -
> which answers my flipside question about where these userids are stored.
> My reading is that there is a server specific database for all the
> userids no matter how many application databases there might be.
> Permissions and rights to objects in any database are stored in the
> server's own private database. This was really a question not a
> statement :) ??
>
> Mike
>

yes. It's called security.fdb. It's not that private. the services API will
tell you where exactly it is on any server, as long as you know the SYSDBA
password.
You cannot change the userid SYSDBA to anything else.
Maybe you should read the metadata/security paper by Geoff Worboys on the
firebordSQL website.

Alan