What is best practice to make parametric selects who's results will be later used in other stored procedures?
(As database evolves then selects can change to output the same data).
For know I use procedure that receive select's parameters and return a cursor with data. (These procedures mostly return cursors with data less than 100 rows.)
I do understand that it is possible to create a parametric views. Still, it requires to change this parameter in code and that can be omitted and lead to errors.
Is there some boundary on return data when you should definitely create a parametric view?