Securing the database from "rogue" developers using tools like MS Access

Securing the database from "rogue" developers using tools like MS Access

 

  

I posted a question regarding this about a month ago and there seemed to
be three solutions to this.

One was using application security - but this doesn't support tracking
updates by user name
Two was using a broker application to track application usage - but this
requires the purchase of a third party program
Three was to provide only Select privileges to the users, but use stored
procedures to provide Insert/Update/Delete capablities.

I'd like to use the option #3, but it occurred to me that users can still
run the stored procedures with "rogue" applications they may write. Is
there any way to prevent that?

Tony

==============================
Anthony Schmidt
President
The Computery Ltd.
One East Main Street
Bay Shore, NY 11706

631-665-8100 Voice
631-969-5988 Fax

http://www.computeryltd.com

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

DB2 & UDB email list listserv db2-l LazyDBA home page