That is the the approach which i would use normally, but duo the capabilities of SQL-Script i would like to find a way whis is better in performance.
A work arround would be a big set of input parameters which are filled with the application itself. Like one procedure to get Options and one for actual execution. A wrapper which singel purpose is to tell the database that a result of a query is not a column but a value in a specific datatype which it could use. Here a graphic of the idea:
As already stated, i would rather use advanced logic of SQL-Script itself instead of a wrapper which comes with performance issues etc.
Perhaps you or somebody else has a good approach on this issue
Thanks and Regards Lukas