Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Sep 27, 2019

Enabling Restrict on Drop clause logic in create table command for db2 LUW

There is a feature called "Restrict on Drop" that should be used by the database designers while creating a table for the db2 LUW database


1) If a database designer uses this "Restrict on Drop" clause for the creation of the table then the 

tables does not get dropped 

2) If a database designer does not use this clause "Restrict on Drop" clause during the creation of the table , then the tables gets dropped irrespective of whether the table has foreign keys and many more dependencies


So Say if the database designer opts for the second option and creates the tables in a database

and in future if he accidentally drops a table then the table gets dropped


Say if that table is referenced by around 10 tables again all thoese references are lost and also

all other dependencies on that table gets losted


So my point is why cant this logic of "Restrict on Drop" be embedded in the "Create table" Command itself so that by default the table goes into a state where it cannot be dropped

Needed by Date Nov 30, 2020
  • Guest
    Jul 7, 2022

    agree with the consensus; if controlled with a registry variable this would be a good idea. I don't think it should be default behaviour for CREATE TABLE

  • Guest
    Feb 21, 2022

    A registry variable (or DSNZPARM for Db2 z/OS) that would implement this is a good idea. The default behavior should remain unchanged, but having the system parameter would be a nice option for those shops choosing to implement RESTRICT ON DROP as a standard. Of course, removing RESTRICT ON DROP to actually drop the table needs to be as simple as today (where it is just a DDL statement) without having to change a system parameter to actually do a drop.

  • Guest
    May 5, 2021

    this will be very good feature to include at the DB2 registry level

  • Guest
    Oct 2, 2019

    It would be helpful for database designers if the 'Restrict on Drop' can be activated through a db2 registry variable

  • Guest
    Oct 1, 2019

    I don't agree with changing the default to enable 'Restrict on Drop'.

    1. As noted by Luis Pontes, previously written scripts could now fail.
    2. I am not sure FK's are in use enough to warrant making this the default in a 'CREATE TABLE...' command. If this is a default all non-FK'd tables would have to disable the option on table create. I am not in favour of what I call 'negative options'.
    3. While making this option a default can protect a developer from making a fatal error, following the proper process when performing a change is the correct method.
      1. Verify a successful backup is available before making a change
      2. Test the change on non-production
      3. Know your database.
    4. It could then be argued that other 'CREATE' commands have a similar option to protect a developer from accidents.

    An optional instance level registry variable would be acceptable.

  • Guest
    Oct 1, 2019

    Innovative feature of DB2 that needs to be activated the registry variable :)

  • Guest
    Sep 30, 2019

    Changing the default behavior will generate too many failures with previously written scripts.

    However, activating it trough a db2 registry variable may be an acceptable option.