Friday 17 August 2012

Advantages and disadvantages with Stored Procedure Universe in SAP Business Objects

 Stored procedures offer the following benefits:

• They encapsulate code. The database operation appears once, in the stored procedure, and not multiple times throughout the application source. This improves debugging as well as maintainability.
• Changes to the database schema affect the source code in only one place, the stored procedure. Any schema changes become a database administration task rather than code revision.
• Since the stored procedures reside on the server, you can set tighter security restrictions. This saves more trusted permissions for the well-protected stored procedure themselves.
• Because stored procedures are compiled and stored outside the client application, they can use more sensitive variables within the SQL syntax, such as passwords or personal data.
• Using stored procedures reduces network traffic. In BusinessObjects XI Release 3.0, you can use stored procedures with Desktop Intelligence and with universes in Designer. You also benefit from
universes that contain stored procedures for Crystal Reports and WebIntelligence.

 

Restrictions apply to stored procedures universes:

• No joins are permitted between objects in stored procedures universes.
• Filters cannot be used on the stored procedure universe.
• You cannot link a stored procedure universe to a standard universe.
• The Web Intelligence supervisor grants access to the database or account where stored procedures are located.
• Not all RDBMSs support stored procedures.
• COMPUTE, PRINT, OUTPUT or STATUS statements contained in stored procedures are not executed.