> > > > Is the original table created with SYSDBA? If so, you're out
> > > > of luck...
> >
> >YES.
> > >
> > >
> > > The first rule of firebird club: you don't develop using sysdba
> > > The second rule of firebird club: YOU DON'T DEVELOP USING SYSDBA
> > >
> > > :-)
> > >
> > > I've seen this happen on many occasions, there should be an FAQ
> >regarding
> > > developing/creating database under SYSDBA account
> > >
> >So what is the point of having the SYSDBA user if you can't really do
> >anything with it?
>
> Whoo-ee, you sure can do literally *anything* with it. That's why you

take

> great care to make sure that the owner of a database and of the objects in
> it are not SYSDBA, if you are going to be in the position where you can't
> have SYSDBA access.
>
>
> >I've used oracle previously, and when creating a DB you use the ORACLE
> >user and create, db, tables, etc.. If you then assign dba privileges
> >to another user, the other user can then create tables, add columns,
> >etc..
>
> Precisely the same is *possible" with FB. However, you got into your bind
> because SYSDBA is the owner of your db and all of its objects and, before
> you parted with it, you forgot to grant the required privileges to you (as
> the ADMIN user, or whatever user you decide to be). The user that creates
> the database is the owner of the database and (separately) the user that
> creates an object in the database is the owner of that object.

I think I disagree here. With Oracle, you can grant "alter any table"
privileges to a user. This means the user can alter a table from which
he is not the owner.

As far as I know, this cannot be done with Firebird.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com