Fabricio Araujo wrote:

>So, each database will have a user list with passwords?
>I don't think is a good idea if you have more than one DB. I also
>admin MSSQL and I like (besides the quircks) the user/login
>coupling. So, all password/basic access right information is in one
>place and more fine-grained info is given to the role (or individual
>users) in the DB itself. This make roles/users db-wide but logins/pass/
>rights to connect DB server-wide.It is AGT (A Good Thing).
>Maybe some SQL commands or external stored procs can handle
>the hassle of maintenance of users/logins/roles on DSQL environment.
>

A reasonable implementation of a security plugin would allow any
database to function as a "security database". At the moment the
security database is found with a magic name and location. Making the
name of the security database be a per-database option would allow one
of the application databases to serve as a common authentication
database for the others.

--

Jim Starkey
Netfrastructure, Inc.
978 526-1376