Thanks for the reply ....

I have no problem using your tool, but I would also like to know what is
'a bit more involved'.

When I look through the System Tables I see the field Owner_Name in
RDB$RELATIONS, RDB$PROCEDURES and RDB$ROLES.

Are the other two tables the 'bit more involved' or is there something else?

I have this one developer that works with me that always wants to update
the System Tables directly. I have always not allowed it and it would
sure be nice to be able to give him a reason why or why not.

Todd

Thomas Steinmaurer wrote:

> > I created the majority of my tables as a certain user. Other tables
> > were created as SYSDBA.
> >
> > Is it safe to change the owner of an object by:
> >
> > Log in as SYSDBA and process the following:
> >
> > Update RDB$RELATIONS
> > Set OWNER_NAME = NEWOWNER
> > Where RDB$RELATION_NAME = OBJECTNAME;
>
> There is a bit more involved.
>
> > Or is there another way to change the owner. I don't want to have to
> > create temporary tables, transfer data, drop existing table, re-
> > create table, copy data back, etc. This is too much work because
> > there are so many dependancies on the tables that have to be removed
> > before I can drop the table.
>
> We have a tool that allows you to migrate a database with several object
> owners to a given user. The download is not available for the public.
>
> Send an email to:
>
> t . steinmaurer @ upscene . com
>
> And request the download link.
>
> --
> 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 <http://www.upscene.com>
>
>

[Non-text portions of this message have been removed]