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 |
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
 Posted - 2010-08-02 : 23:40:45
|
| I have a requirement where in, data from the DB needs to be accessed, only from views. The views represent the tables 1:1The developers should access only the view, not the tables. I need a mechanism to restrict the developers from accessing the data from the table. Following is a possible solution, 1. Create a DDL trigger for create/alter proc2. In the trigger get the proc body and search for table name3. rollback the code, if table name found Is there a better way?------------------------I think, therefore I am - Rene Descartes |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2010-08-03 : 00:04:20
|
why not just don't grant the SELECT rights on the table to the developer ?
KH[spoiler]Time is always against us[/spoiler] |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2010-08-17 : 10:14:04
|
| do they have permissions to create/alter objects?if they're dbo, i don't think you have some say on it, unless you create that trigger on a server wide scope...initially I thought you can set explicit denies on the table for the developers then I read the line about procedures--------------------keeping it simple... |
|
|
|
|
|
|
Stored proc and data access