IBM Security Guardium 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:


Post your ideas

Start by posting 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 offering manager 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.


Post an Idea

To post a new idea - click on the "Add a new idea" button and select the appropriate capability area this idea relates to. Do provide requested information to allow us to get a better understanding of your request. If 'Guardium Data Protection' capability is selected, you will be prompted to select the category/product the idea relates to. If you are not sure of the category/product your idea would fall under, then select 'IBM Guardium Other' in the drop down list and proceed from there.


Please note: The purpose of the Ideas Portal is to tap the creativity of the Guardium Data Protection community so that we can enhance the product for everyone! If you need to report a defect or get help, please use our normal support channel. Click here to open a support ticket.


For IBMers, click here to submit an idea on behalf of a customer, if the customer prefers to keep their use case and idea private.

Add “WITH(NOLOCK)” possibility in the Classificator sample gathering SQL

The Classificator has only read privilege in the Customer Database, just reading sample rows from the table(s). In a heavily used MSSQL environment, the Classificator SQL’s running time can be very large, and because of the locks, can be interference/blocks tables and business processes/applications. For the read SQLs it is enough the Uncommited READ Transaction Isolation Level, it can be specify using “with(nolock)” option. The previous SQL is using this option “with(nolock)”, but the following (the actual) SQL (that querying the sample records) does not contains it.

Add a possibility to use this option, this possibility can be for example an additional advanced checkbox, where it can be enable.

  • Guest
  • Jul 25 2022
  • Delivered
  • Admin
    RAJESH VENKATASUBBU commented
    6 Dec 06:11am

    Support for this request is delivered with Guardium Data Protection v11.4 patch bundle p460 which is available in Fix Central.


    Thanks,

    Data Security - Product Management

  • Admin
    RAJESH VENKATASUBBU commented
    20 Sep 07:48pm

    This request is planned to be addressed with a patch update for Guardium Data Protection v11.4 and v11.5 in the near future.


    Thanks,

    Data Security Product Management Team


  • Guest commented
    10 Aug 07:25am

    Our main goal is to use Read Uncommited Transaction Isolation Level with this Sample collecting SQL statement too. Because the Classification Process is “just reading” during the running time, and this Read Uncommited level provides the less blockades, most parallelization, less locks.Andrzej (the Customer MSSQL DBA) is highlighted, in the MSSQL the HINT and the SET statement in some cases can be a different (from transaction isolation level point of view), because the HINT is just a suggestion to the MSSQL Optimizer, but the SET is choosing the proper level.


    We have two pictures from the DBA that came from the trace and show the differences between the HINT and the SET, see the tran_isolation_level column.


    We would like to ask you, to use the SET.


    Because the usage of the “SET TRANSACTION ISOLATION LEVEL READ UNCOMMITED;” additional statement is better way than the “WITH (NOLOCK)” hint at the end of the original statement.

  • Admin
    RAJESH VENKATASUBBU commented
    5 Aug 10:37pm

    Hello, thank you for submitting your idea / request for enhancement for Guardium Data Protection!

    We are reviewing this request, we will get back to you with our findings.


    Thanks,

    Data Security - Product Management

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.