IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Ability to re-create views and procedures without dependent objects being dropped

Some objects in a database often depend on other. As an example, if there is a view, another view can be built upon it.
Private and public synonyms can be created for those views, and permissions given to various users on those views.
If the first view needs to be recreated (change of code), it needs to be dropped and created again.
When it is dropped, all of the dependent objects are consequently dropped - the other view, all the related synonyms and permissions, and so on, recursively.
The DBA has no warning of it happening, and later has to guess or use any other complex method to conclude which objects were dropped
and has to recreate all of them.

What is needed is some kind of ALTER VIEW statement (or CREATE OR REPLACE), that will recreate only the view at hand, without dropping dependent objects.

There is a similar situation regarding stored procedures: recreating a procedure or function means all the permissions on it getting dropped.

In an environment with many database users where access control is implemented with views, private synonyms and stored procedures, ALTER VIEW and ALTER PROCEDURE would really cut a lot of DBA work.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 24 2018
  • Future consideration
Idea Priority Medium
Customer Name University Computing Centre
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions