crmitchell (4/22/2013)
opc.three (4/22/2013)
crmitchell (4/22/2013)
Eric M Russell (4/18/2013)
Dree Vasquez (4/18/2013)
Hi AllIf you're a member of sysadmin, then you can grant or deny whatever privillages you know are really required. You can even edit and recompile the stored procedures too. Don't let some 3rd party tell you how to manage your database.
As a counter to that you should remember that the code whether stored procedures or otherwise should have been tested and signed off before being put LIVE. This testing may and change control may be governed by statutary requirements and so altering it without a full retest may have legal implications. As such you should not be changing the stored procs but instead requiring the developers to do so.
It depends on the shop. Some DBAs have carte blanche to change code when it makes sense, i.e. when the changes relate to database security or performance. Other times those tasks fall to a developer.
On the other hand it is reasonable to require the developers to produce the code such that it will work correctly on a server with much more restrictive permissions.
As a developer I would expect very liberal rights on the develpment server - definitely DBO and probably SysAdmin. I would expect TEST to be more restricted - no SYSADMIN, maybe DBO but probably only DBREADER, DBWriter and appropriate EXECUTE permissions and minimal rights on the LIVE box.
Well I'm a developer but as I said I would expect that on DEV and would expect to need to justify it in TEST - it may be needed when promoting to TEST but normally I would not normally expect it after that stage is completed. Older code may still require it but it should be the exception rather than the rule. It should not be expected for LIVE.
The only thing I would want on LIVE over and above the basic access everyone would have would be the ability to view but not alter server settings and the database objects to aid with diagnosing problems. In some cases the sensitivity of LIVE data may mean that even that level of access would not be appropriate.
Ideally for LIVE the code should be set up to run with execute permissions on specific stored procs only and no general DB access.
Judging by your response I thought I would point out that You gave them dbo?[/url] was a link to a blog post, not really a question or comment directed at you. I consider myself a Developer first, and a DBA second. In some shops your expectations will not be met. You may be granted db_owner membership in DEV, read-only and VIEW DEFINITION in TEST, and nothing in LIVE, because sometimes you will not be allowed to see transactional data in LIVE and non-LIVE environments will be scrubbed of PII. At the end of the day if the code is untested in DEV it should not even make it to TEST, let alone LIVE. By the time it makes it to LIVE developers should not need to worry. Of course this is best case scenario, but that's how it goes in some shops. In some extreme cases access to LIVE can be granted temporarily to troubleshoot an issue that cannot be recreated in DEV or TEST, but that would require an approval for access to PII. You can see how this could motivate developers to produce fully-tested code that can be deployed in a repeatable way such that it runs in LIVE the same way it runs in DEV, a nice ancillary benefit to having a locked down LIVE environment.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato