SQL Server Performance

Calling DB2 procedure

Discussion in 'SQL Server 2005 Reporting Services' started by ramasubbup, Apr 11, 2006.

  1. ramasubbup New Member

    We are facing problems while creation reports from SSRS working with DB2 as a database. Stored procedures defined on DB2 returns data to Reports.

    We have tried to call DB2 stored procedure from Report Designer in following ways

    1. Call the DB2 Stored Procedure from Report Designer with command type as Text
    { CALL SG4OPROC.P8G4ARTO(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) } – This works at design time but we are not able to pass parameters to stored procedure at runtime from report.

    If we call the Stored Procedure with the same way as SQL Server i.e. appending parameters with '@' symbol, the query is not parsed by DB2 for execution.

    2. Call the DB2 SP from Report Designer as command type as Stored Procedure
    SG4OPROC.P8G4ARTO – The out put parameters from Stored Procedure are not identified by the report and gives error that Stored Procedure is not found.

    Thanks for any pointers

  2. satya Moderator

    This not a soution, but have you tried asking the same in DB2 related forums, may check IBM for relvant information.

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. ramasubbup New Member

    Thanks sathya.

    But I can't get you clearly when you say 'This is not a solution'.

    I strongly feel that we have to figure out in SS RS to see how to call a DB2 stored procedure from SS RS instead of asking IBM.

    Take a sample case where a 3rd party is providing reporing services to sql server.
    If that reporting service does not work properly in calling a sql server stored procedure, we cannot ask Microsoft about it.

    In the same scenario we cannot ask IBM, how to invoke db2 procedure from SQL Server
    Reporting services.

    Correct me if I am wrong.

  4. satya Moderator

    I mean to say my post is not a solution... but a suggestion [<img src='/community/emoticons/emotion-1.gif' alt=':)' />].<br />Right too many are involved here, then try to ask vendor to fix the problem, out of interest searched on google returned below links about db2:<br /<a target="_blank" href=http://www.devx.com/IBMDB2/Article/27818>http://www.devx.com/IBMDB2/Article/27818</a><br /<a target="_blank" href=http://www.dbazine.com/db2/db2-mfarticles/lawson1>http://www.dbazine.com/db2/db2-mfarticles/lawson1</a><br /<a target="_blank" href=http://www.mcse.ms/archive94-2004-8-1009406.html>http://www.mcse.ms/archive94-2004-8-1009406.html</a><br /><br />HTH<br /><br /><hr noshade size="1"><b>Satya SKJ</b><br />Microsoft SQL Server MVP<br />Contributing Editor & Forums Moderator<br /<a target="_blank" href=http://www.SQL-Server-Performance.Com>http://www.SQL-Server-Performance.Com</a><br /><center><font color="teal"><font size="1">This posting is provided “AS IS” with no rights for the sake of <i>knowledge sharing.</i></font id="size1"></font id="teal"></center>

Share This Page