jim.drewe (12/3/2013)
If a DBA could control the database, control the access, and control the manipulation of the data, it could get pretty ugly. That would be too much power to reside in a single individual for a large company.
I worked in a medium size bank for many years. I was the production DBA, the dev DBA on major systems (SQL, Oracle, etc.) as well as doing ETL between the stove-piped systems.
In the 10+ years we had only one high level embezzlement case. That also caused us to rebuild the whole Fixed Asset system. (He embezzled from a different source but built the FA system in his head and had no documentation.)
But the whole system we developed worked off the two "man" rule. Basically I would do whatever as commanded by the accountant. She had to verify it. The list of changes were written down.
But realistically if you hire people without honor, honesty, and respect -- they are going to find a hole in the system to exploit.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.