> So that means, like Thomas had said
> "Pretty simple, don't use SYSDBA as owner for deployment!! !"
> will not work.

It will work in regard to no need to share SYSDBA with other
applications, fiddling around with the password of this "shared" user
... :-)

Once you have moved your database and the objects inside to another
owner, you can lock SYSDBA out by:

* Connect with the new owner to the database
* Execute:

INSERT INTO RDB$ROLES
(RDB$ROLE_NAME, RDB$OWNER_NAME)
VALUES
('SYSDBA', <your connected owner>);

COMMIT;


Not a bullet-proof lock out thingy though, but it eliminates e.g.
connections via SYSDBA by accident during development, ...


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/