Subject | Re: How to prevent SYSDBA to connect to database |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-02-19T18:07:59Z |
--- In firebird-support@yahoogroups.com, Pablo Sánchez <pablos@a...>
wrote:
a) database was created not by SYSDBA
b) there are not objects created or altered by SYSDBA in this database
c) there are not grants made by SYSDBA in this database
else FB see conflict user name - role name on role creation. It is
related not to SYSDBA only, to any user mentioned as 'owner' or
'grantor' in system tables.
Best regards,
Alexander.
wrote:
> Hi, that could be nice, but i get in isql :Pablo, this trick can be used only if:
>
> SQL> create ROLE SYSDBA ;
> Statement failed, SQLCODE = -607
>
> unsuccessful metadata update
> -user name SYSDBA could not be used for SQL role
> SQL>
>
> It could be nice, at least to keep some lurkers out of the job.
>
a) database was created not by SYSDBA
b) there are not objects created or altered by SYSDBA in this database
c) there are not grants made by SYSDBA in this database
else FB see conflict user name - role name on role creation. It is
related not to SYSDBA only, to any user mentioned as 'owner' or
'grantor' in system tables.
Best regards,
Alexander.