Public Role for SQL 2000



For SQL 2000, I see that the Public role has some privileges like SELECT,
UPDATE, DELETE, & EXECUTE, permissions for some User's database objects
(Tables, views, &Stored procedures .)



Is that a security concern?

What will happen if I remove these privileges or revoke them?

Will that effect the rest of the users?



I read many threads on the internet, but no one could tell me the answers
for the 3 questions above.

Thanks in advance.




.



Relevant Pages

  • Re: Mixed mode vs Windows integrated securiy
    ... > software that keeps track of money. ... > software need SELECT,INSERT,UPDATE and DELETE privileges to the tables ... I'd have everything in stored procedures and the ... For Blogs, FTP, Mail, Forums, Members Product Areas ...
    (microsoft.public.sqlserver.security)
  • Re: sp_OACreate
    ... you are granted execute privileges to the wrapper, ... these procedures in your own T-SQL stored procedures, ...
    (microsoft.public.sqlserver.dts)
  • Re: sp_OACreate
    ... you are granted execute privileges to the wrapper, ... these procedures in your own T-SQL stored procedures, ...
    (microsoft.public.sqlserver.dts)
  • Re: ORA-00980, but object exists!
    ... This could be due to privileges inherited from roles. ... stored procedures will not see referenced ... with this as well as some sort of problem with some of the schemas ...
    (comp.databases.oracle.server)
  • Re: cdrecord local root exploit
    ... Notice the restricted permissions on /usr/libexec/screen (it's made ... we wanted to give screen both privileges (of group chkpwd ... To make this fit in with packages (yes, ... There's simply no reason to do that: a non-root pseudo-user won't be ...
    (Bugtraq)