Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
danyeung
Posting Yak Master
102 Posts |
 Posted - 2008-01-15 : 11:02:45
|
| A login named UserLogin1 has db_dataReader and db_dataWriter roles, and three schemas which are db_owner, dbUser1, and dbUser2 in a database named Database1. I wanted to have some tables for read-only, so I right clicked on the table and select properties. In the Permissions tab, I added UserLogin1 and checked Alter, Delete, Insert, Take Ownership, and Update under Deny. It worked for schema dbo only. I did the same steps for the tables that have schema dbUser1 or dbUser2, but UserLogin1 I added didn't stay. Why? How can I make those tables read-only?Thanks.DanYeung |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-15 : 23:22:47
|
| Try set it in schema properties -> securable. |
 |
|
|
danyeung
Posting Yak Master
102 Posts |
Posted - 2008-01-16 : 10:45:50
|
| I found out why but not sure the best way to handle it. The schema owner for dbUser1 was dbUser1 and the schema owner for dbUser2 was dbUser2. If I changed the schema owner to dbo, it worked. I don't know how much impact or side effect if I change the schema owner to dbo for dbUser1 and dbUser2. Any suggestions what I should pay attention to?Thanks.DanYeung |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-16 : 23:30:00
|
| No impact if no object in those schema. |
|
|
|
|
|
|
Assign permissions for individual table.