Discussion on:

Understanding roles in SQL Server security

I am gathering information on advantages of SQL 2000 server over SQL 7 (Enterprise/Std. editions).

Thanks in advance

Using roles for groups can be a good way of implementing security in some cases but have found that application roles offer a better level of insultation from the standard user and in many cases allows them to use the database in an easier mode thana database role.

Maybe in the next article we will look at Application roles. Apologies for the dll typo. We should have seen that one.

Not sure if this was erroneously insincere or sincerely erroneous.
db_ddladmin: Members can run dynamic-link library (DLL) statements.
I think it would be called db_dlladmin if that were the case. DDL is Data Definition Language that define data structures. So users in this role can do things like CREATE TABLE.

"db_ddladmin: Members can run dynamic-link library (DLL) statements": Absolutely incorrect.
DDL is not the same as DLL. DDL (Data Definition Language) Admins can script object definitions, for instance: CREATE TABLE MyTable...
Regards.

not helpful. these are all database roles not server roles. i am particularly interested in restricting the Server Role called Security Administrators which allow for management of logins for the server. i want our DB Admin to have everything but this capability.

You said that "db_ddladmin: Members can run dynamic-link library (DLL) statements" and that is FAR from correct. The db_ddladmin is a role that enables users to execute DDL (Data Definition Language) scripts against the DB. Take a look at MSDN docs (http://msdn.microsoft.com/en-us/library/ms190667%28v=sql.90%29.aspx) before trying to figure out something you don't know/remember, ok?

http://msdn.microsoft.com/en-us/library/ms189121.aspx