SQL Server 2005 permissions required by public

110 pts.
Tags:
SQL Security
SQL Server 2005
SQL Server 2005 security
SQL Server permissions
Our security madates that ALL object permissions be removed from"public". After doing that, no one can see their tables or do anything. What are the absolutly NEEDED permissions required by public (Execute, Select, etc.)?

Software/Hardware used:
SQL Server 2005

Answer Wiki

Thanks. We'll let you know when a new response is added.

The permissions granted to the public role should be left as they are. In SQL Server 2005 and up they are already setup for the lowest set of permissions needed.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • VelameLaCosa
    But the permissions have been REVOKED and users cannot get to their data. One user got message: The SELECT permission was denied on the object 'configurations', database 'mssqlsystemresource', schema 'sys'. Users have gotten similar errors on other objects. I need to find out what is absolutely necessary for SQL Server to work normally.
    110 pointsBadges:
    report
  • VelameLaCosa
    [...] A member is having difficulty dealing with the SQL Server 2005 permissions required by public, and Mrdenny is trying to [...]
    0 pointsBadges:
    report
  • Denny Cherry
    You need to regrant the permissions back that you revoked. SQL Server 2005 ships in a much more locked down configuration that SQL Server 2000 did. The old policies of removing all the permissions don't work in SQL Server 2005 because you run into all sorts of problems like you have. I don't have a SQL Server 2005 server handy, so you'll probably want to install another instance, identify which permissions should be there by default and put those permissions back in the master database. That or restore your system database from a time before you changed the permissions.
    66,085 pointsBadges:
    report
  • VelameLaCosa
    [...] revoking database permissions that you don’t understand what do, don’t come to be complaining that your SQL Server isn’t working correctly.  Guess what, those permissions where there for [...]
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following