Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Sep 1, 2017

Implement an option to ignore trigger on update

Add an option that allows to ignore triggers on update/delete

Use Case:

I'm having a stored procedure that updates a technical field on tables. these updates are slow, because there are triggers on some tables. I know that these updates don't have any impact on business data handled by the triggers, so I'd like my updates to run faster without triggering anything, but just for my stored proc.

Idea priority Medium
  • Guest
    May 14, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    Most triggers are used to enforce business logic, so allowing users to circumvent the trigger would leave the underlying data exposed to potential security or data violations.

    If there is a performance critical data operation that can be accomplished during a period when its safe to run without the trigger to gain a performance advantage, you can consider using ALTER TRIGGER DISABLE / ENABLE to temporarily remove trigger enforcement from the table.

  • Guest
    Apr 16, 2018

    Triggers are used for many purposes, but one key aspect is to implement business logic and/or data validation.
    Depending on what a customer is using the trigger for, allowing any user to just ignore a trigger would possibly cause data violations and could be a security exposure.