Hi, ADS-team. Why you decided to limit the right to disable all triggers? For ver.11 "no permissions are required for users to disable triggers on themselves", but now for ver.12 "In order to disable triggers on the current connection, membership in the DB:Admin group is required". We can't include all our users in DB:Admin group for security reasons and without that our ERP-application has stopped working :(. How is it possible to get around ?

asked 20 Nov '15, 15:03

Igor's gravatar image

accept rate: 0%

Hi Same applies to me. For batch procesing I need to disable triggers otherwise it will be to slow.

(21 Nov '15, 20:42) Marcus Herz

Yes, but not only for that. Sometimes it is necessary to bypass the logic triggers. Independently users do not do, and enjoy the scripts that are written in the program

(22 Nov '15, 09:55) Igor

Hi all. When can we expect an upcoming service pack of ADS12? Almost half a year we are already waiting it or you do not plan to support ver.12 ? It's a pity!


answered 03 May '16, 01:27

Igor's gravatar image

accept rate: 0%

The behavior change in ADS 12 was introduced to resolve security concerns. The decision to implement was taken after due discussion, and security implication was considered more important.

Now, however we are discussing this again, and are looking at the possibility of providing a work around so as to avoid breaking current application. If feasible, this will be provided in an upcoming service pack of ADS12.



answered 23 Nov '15, 15:03

Parag%20Mahadane's gravatar image

Parag Mahadane
accept rate: 4%

Thank you. We are looking for it

(24 Nov '15, 13:06) Igor

IIRC permission check within a stored procedure does not happen. So, as a workaround, you could try to bypass it with a stored procedure:



execute procedure runsql('execute procedure sp_DisableTriggers(...)');


answered 24 Nov '15, 18:19

Joachim%20Duerr's gravatar image

Joachim Duerr
accept rate: 18%

Many thanks, Joachim.

(24 Nov '15, 18:48) Igor

Unfortunately this method dosn't work - can't disable triggers from procedure

poQuery: Error 7200: AQE Error: State = HY000; NativeError = 5154; [SAP][Advantage SQL Engine][ASA] Error 5154: Execution of the stored procedure failed. Procedure Name: runsql. Error 7200: AQE Error: State = HY000; NativeError = 5196;
[SAP][Advantage SQL Engine][ASA] Error 5196: The parent table or database has triggers disabled. Cannot disable triggers from within an AEP or trigger. - EXECUTE IMMEDIATE -- Location of error in the SQL statement is: 21 Error in stored procedure: runsql

(24 May '16, 06:10) Igor
Your answer to the original question.
If responding to a request for additional information, please edit the question or use the comment functionality.
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 20 Nov '15, 15:03

Seen: 2,308 times

Last updated: 24 May '16, 06:10

Advantage Developer Zone Contact Us Privacy Policy Copyright Info

Powered by Advantage Database Server and OSQA
Disclaimer: Opinions expressed here are those of the poster and do not necessarily reflect the views of the company.