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 Planned for future release
Workspace Connectivity
Created by Guest
Created on Jun 21, 2021

Redshift connector slow in IIS DataStage for Insert/Update

We have a use case in which we need to process records from IIS DataStage into an aws Redshift instance. When using the stage as currently implemented, we're seeing a throughput that averages 2-6 records a second which is far below the acceptable range when considering load sizes in the range of hundred of thousands. Additionally depending on your configuration, the connection to Redshift will eventually timeout after several hours. Currently the stage implements inserts and updates using a JDBC insert which is not a best practice according to aws documentation. Instead the stage should be using the Redshift COPY command to bulk load the finished data set which is far faster than inserts.

Needed by Date Sep 1, 2021
  • Guest
    Jan 20, 2022

    We are having the same performance issue using RedShift connector stage when inserting data into RedShift database from DataStage.

    When we use RedShift Connector stage, It's inserting 22 rows per second.

    When we reached IBM Support, they provided the documentation for JDBC Connector stage. After implementing suggested changes for JDBC, Job completed inserting 5 million rows in 16 minutes at a rate of 5377 rows per second. Performance slightly improved and but still it’s not acceptable. We used 500,000 as record count and 500,000 batch size in the JDBC connector stage when processing 5 million rows.

    Using the same set of data and Inserting 5 million rows into Netezza, job completed in less than a minute and processed 421,000 rows per second.

    Using JDBC Connector stage, when we try to read and extract 5 Million rows from RedShift Database, it's completed in less than 1 minute and processed around 350,000 rows per second.

    Using RedShift Connector stage, when we try to read and extract 5 Million rows from RedShift Database, it's completed in less than 1 minute and processed around 160,000 rows per second.

    Reading data from RedShift database using the RedShift connector stage or JDBC Connector stage, we do not see any issues.

    The issue we are having is only, when inserting data into RedShift database.

    We opened PMR with IBM Support : Case TS008045974.

    They stated that, it's an enhancement request and suggested to update here.

    Please let us know, if IBM is currently working on any enhancements to address the performance issues when inserting data into RedShift database from DataStage and when can we expect latest Patches for the RedShift connector and JDBC Connector stages.

  • Admin
    Virginie Grandhaye
    Jul 7, 2021

    Thanks for submitting this idea.

    After analysis, it appears that we could consider this item in the future if we get enough demand for that. Changing the status to "Future consideration".