SQL Command

440 pts.
Tags:
AS/400
SQL
Hi friends (again), It's possible to prohibit a update option on a SQL Command to a guest user ?

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Gilly400
    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.
    23,730 pointsBadges:
    report
  • GAC
    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
    300 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following