> > > without a clear idea of where the security changes are going
> > i.e. how they
> > > are to be implemented, it's difficult to propose a solution.
> > > per database security will no doubt introduce yet another layer of
> > difficult
> > > workarounds for certain tasks but does anyone (including Alex Peshkov)
> > have
> > > an implementation guide to follow on this?
> > > I'm not familiar with DBWorkBench grant manager - how does it
> > wrestle with
> > > this task?
> >
> > If you used a sysdba password when registering the server, it
> > will use that
> > (for each database) to get a list of users know to the server.
> > Enter it once
> > and it will be used wherever the Services API needs it.
> >
>
> so that means that all grants are caried out by SYSDBA rather than by the
> DBOwner?

No, I mean that the list of available users is fetched by using the SYSDBA
account.

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com