RELATED QUESTIONS
Answer Wiki:
Thanks friend, SQL on AS/400 and no in SQL Server.
Hello Silvarb,
if you are using MS SQL 2005 <a href="http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1127863,00.html">you can read this</a>, otherwise please be more specific and post more information on the SQL you are using.
Bye
=============================================================
If the user interface to SQL is through QM, then yes, you can prohibit the use of UPDATE or any other SQL statement. But if other interfaces are available, particularly STRSQL, then no, you can't.
Network interfaces can be restricted with exit programs, but it's practically impossible to enforce for actual statements due to the extreme variety of potential formats. I.e., an UPDATE doesn't have to done via a statement that begins with "UPDATE".
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Hi,
If you’re using the AS/400 you can restrict the user from updating files using object level security – this should also prevent SQL updates, but will also prevent updates through application programs. It’s probably better to restrict the use of SQL for the user. You could revoke the authority on the STRSQL command for example.
Regards,
Martin Gilbert.
Hi there,
“Developing” over Martin’s contribution, if you work with groups you can assign privileges according to the kind of user and then just add that (those) user profiles to the group, preventing any guest user from using the STRSQL cmd.
Another option is to use an exit point program to the database server (more complicated, but an option anyway).
Regards