Product specifications

Connection Server is able to manage data from data sources that result either from SQL query or stored
procedure execution.
Stored procedures are SQL scripts that are stored as executable code in an RDBMS. They can receive
arguments and return data.
Stored procedures for the following databases and network layers are supported in the BI platform:
• DB2 UDB and iSeries through CLI driver
• Sybase Adaptive Server through CTLIB
• Javabean
• DB2 UDB, Derby, HSQL DB, Informix, MS SQL Server, MySQL 5, Oracle, and Sybase, all through
JDBC
• Oracle through OCI
• DB2 iSeries, Informix, MS SQL Server, Sybase ASIQ, and Sybase SQL Anywhere, all through ODBC
• MS SQL Server through OLE DB
4.3.1 Supported database capabilities
Connection Server only supports stored procedures that return data as result sets, that is, tables. This
means that the stored procedure cannot return integers, strings, or cursors and must always contain
SELECT statements. Plus, supported stored procedures must not contain OUT or IN/OUT parameters.
In addition, COMPUTE, PRINT, OUTPUT or STATUS statements contained in stored procedures are not
executed.
Caution:
These restrictions are not valid for Oracle stored procedures. Refer to next section for learning about
supported Oracle stored procedures.
Connection Server supports Oracle stored procedures inside a package. The package name is returned
as the catalog name. This behavior is valid for Oracle CI and JDBC network layers.
Note:
For more information about using stored procedures, refer to the Universe Design Tool User Guide .
4.3.2 Oracle stored procedures
The supported Oracle stored procedures are the following:
• any PL/SQL procedure that returns result sets through a REF Cursor
• PL/SQL stored procedures that have one IN/OUT REF cursor variable parameter and no OUT
parameter
2012-03-1529
Learning data access specifics