ZZartin (8/29/2015)

---

xsevensinzx (8/29/2015)

---

Ed Wagner (8/28/2015)

---

Scott, I agree with you that the point is to run a business. You raise a good point about perspective. It may be that cutting off all access could be bad for business, but so could having everyone with a computer having the ability to run whatever queries they want against the production database. It might impact performance...just a bit anyway.

Going back to a previous post, the DBA and management needs to have a serious conversation, focused on the needs and wants of the employees.

As for me, I'd vote no.

I struggle with this a great deal on my end because the data is primarily used for reporting only. While it's good to restrict, the end users who pay your salary may defy everything holy and still insist due to lack of understanding the reproductions of their actions.

I get around this now by simply providing reporting data marts for the business case. The only issue is the bottleneck of creating a the data mart, but at least it's separate, read only and totally secure for only the end users for that specific business case.

One of the dangers of letting end users create their own reports is that they will, for example end user A goes in and sets up a report doesn't get the results expected and tweaks his query until he does get the results he wants but user B goes in and sets up a query for the same reason but doesn't tweak it. Now they both show up to a meeting with conflicting data and it's the DBA's problem to fix not their's.