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 |
|
vdavid70
Yak Posting Veteran
67 Posts |
 Posted - 2006-11-20 : 06:05:29
|
| I manage a production sql server 2000 database on a windows 2000 server and have to give some developers (dbo) permissions on the sql database to alow them create and edit views in the database.I am not comfortable with this arrangement, because i beleive it gives them right to do other things within the database e.g editing the tables within the database.Therefore, what is the best way to limit a users permission in sql server to just been able to have create and edit permissions on the views and therefore select permissions on the tables within the database. |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2006-11-20 : 10:33:47
|
| Let them go nuts on a development server, and make them hand over the scripts for their changes when they want to make a production change. |
 |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2006-11-20 : 11:03:54
|
| Agreed! The best way to "limit permissions" is to not give them permissions at all.You absolutley need a "development" environment which the developers have full access. Any changes to the production environment should be only done via scrips by a dba accountable for that environment. Where I work now we have 4 environments (dev, qc, acceptance, prod) Nothing goes to prod that hasn't run the gauntlet of the other environments.Be One with the OptimizerTG |
|
|
|
dewacorp.alliances
452 Posts |
Posted - 2006-11-22 : 06:13:09
|
| Hi TGWhat is QC? Is this query server?Thanks |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2006-11-22 : 06:22:53
|
| I think he refers to "Quality Control"...Peter LarssonHelsingborg, Sweden |
|
|
|
|
|
|
SQL View Permissions