View Single Post
  #30 (permalink)  
Old November 29th, 2013, 01:04 AM
maurices5000 maurices5000 is offline
Authorized User
Points: 94, Level: 1
Points: 94, Level: 1 Points: 94, Level: 1 Points: 94, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2013
Posts: 24
Thanks: 7
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Imar View Post
datareader and datawriter should be enough if your application doesn't modify the database structure.

Are you maybe using Entity Framework code first that modifies the database schema? In that case, ddladmin would be the role to add. dbo is typically to much.

Also, are you configuring group membership and not schema ownership?

Imar
Nope! Not using entity framework. I am using stored procedures though. In the email to me you said: "Not sure if you've seen my reply, but in case you haven't: DataReader and DataWriter should be enough if your web site only reads and writes to tables and views. If it also alters the database it needs DDLAdmin permissions, and if you have stored procedures those require execute permissions. DBO shouldn’t be necessary and typically means the account has too many permissions." Is there an account that is better than DBO for execute? Would I still need dataReader and DataWriter?

Last edited by maurices5000; November 29th, 2013 at 01:07 AM..
Reply With Quote