Not knowing all of the details..The limited security option is the best
way to go. If you are wanting to track or audit the users updates, use
triggers on the tables that populate or defaults to track userid. You
should be able to add a field such as change_user and have it default to
the userID
MM


-----Original Message-----
From: Anthony Schmidt
[mailto:db2udbdba-ezmlmshield-x83592943.[Email address protected]
Sent: Thursday, April 28, 2005 1:47 PM
To: LazyDBA Discussion
Subject: 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
______________________________________________________________________


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html




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