Friday, August 21, 2015

Read Permissions on Production Server

what is the harm giving read only access to developers?


2 Scenarios:



1. If I have a very low OLTP server, few databases with only few applications, then there is no harm in giving Read only access to developers.

but

2. what about on a high oltp server, where some developers try to read data from 1 million rows
Select * from Table---? 1 million
or a badly written query; joining multiple tables, query is not optimized or not using proper indexes?

this could Lock tables, use Maximum CPU, have high DISK usage and this could bring production/ application connected to database down .

 an alternate option is replicate the database, tables to a different server(Subscriber) and ask developers to read the data from Subscriber.


Conclusion:
Be careful on giving Read access to Developers and decide whether to give or not based on 2 scenarios mentioned above


No comments:

Post a Comment

https://blog.sqlauthority.com/2009/06/27/sql-server-fix-error-17892-logon-failed-for-login-due-to-trigger-execution-changed-database-context...