From: "samcarleton" <scarleton@...>

> We have DB data issue where data is duplicated in two tables. When the
> first table is updated, a trigger updates the second table.
>
> Ideally we would like to lock down the database so that the second table
> cannot be updated by the user/application. Can that be done, if so, now?
>
> It is my understanding that some DBA's like to lock users/applications out
> of the tables and do that with stored procs. Is there some way to setup
> the security such that triggers and stored procs can modify the table but
> the user/application cannot?
>

You really can't "lock it down" since any triggers and procedures will run
under the users login credentials.

The only way I can think of would be to create a simple (or complex for
safety) flag system where the before insert/update trigger on the second
table would check some other table for a flag which says it's running from
the synch procedure. If the flag isn't set, the before insert/update trigger
could cancel the changes.

HTH

Woody (TMW)