Why use 'WITH RESULT VIEW'?

[Former Member]

I have found many threads explaining how to use the 'WITH RESULT VIEW' option, but almost nothing explaining really why and when.

Also SAP's official documentation (incl. OSS) seems (to me) devoid of any such explanations.

Specific questions in this regard that I wonder about are:

- Wherein exactly lies the assumed performance advantage 'WITH RESULT VIEW'?

- Does it affect parallellization (I assume not)?

- What about calls from a procedures calling another procedure?

Somebody out there ready to lift the veil on the 'WITH RESULT VIEW' option for me?

[lbreddemann · Accepted solution]

Not quite sure there is a veil to be lifted, but let me have a shot at this.

Who made claims that providing a result view would improve the performance of a stored procedure?

How should that work?

Generally you may consider the result view simply as an additional way to access the result set of your procedural code. Maybe you want to use the result data with a framework that doesn't support CALL commands, but that does support SELECT.

In such case, having a view comes in handy, doesn't it?

I am not aware of any impact to the execution of the code in relation to your actually not so specific question points.

- Lars

[Former Member · Accepted solution]

Thanks for this answer clearing up the fog.

Yes, indeed a nice option in some cases.