I tend to attribute this to MS (SQL Server) style programming. The app owns the
database, therefore is dbo, Many duhvullpers that I meet don't even realise
that you can have other users in a SQL Server database.
Also, the pressure to deliver yesterday, with no database knowledge to speak of, may lead
some to just require "run as administrator" (everyone works in Windhoze these
days) in stead of determining exactly which permissions are required.. lazy... perhaps.
Eazy certainly.
In my experience there is no valid case. DBA should be limited to as few
individuals as possible, which excludes applications outright.
Cheers,
Tony
On 13/07/16 21:42, rob@xxxxxxxxxxxxxxxx wrote:
I still see DBA rights being granted to applications. So before I get up there and make a
blanket statement - "if you do this, you are just being lazy, stupid and a few other
adjectives." Can anyone think of a use case where granting DBA to an application is
valid? I have been racking my brain and can't come up with any use case where that is
acceptable.
-Rob
===================================
Robert P. Lockard Oracle ACE
Winner of the 2015 Oracle Developers Choice Award for Database Design
President Oraclewizard.com, Inc.
*The question is not “who is going to let me,” it's “who is going to stop me."
Ayn Rand*
(cell) 571.276.4790
(office) 410.766.6960
(fax) 410.766.0332
twitter @navonpilot
youtube https://www.youtube.com/user/n4281k
blog: http://www.oraclewizard.com
