In our case, we distribute an end user application with proprietary
lookup data. Currently, all an end-user has to do is replace the
security.fdb to gain SYSDBA privelages.

Having the database either bound to a specific security.fdb file or
having the users stored in the database itself would eliminate (well,
greatly reduce the likelihood of) this problem.

Kevin Lingofelter


On Fri, 24 Sep 2004 16:48:13 -0400, Alexandre Kozlov
<alexandre_kozlov@...> wrote:

> Ladies and Gentlemen,
>
> is it really good idea to put these things into database. What is the
> benefit ? May be for small organization it's OK but for large one it's no so
> good. To remove any information about users from database I would even like
> to deprecate 'GRANT role to user' statement for keeping this information
> also in central security database (of course, DB server should know aliases
> and addresses of all databases it is allowed to work with)
>
> Alexander
>
>
> Yahoo! Groups Links
>
>
>
>
>