I rarely create views because when joining table you might have to join with table hints, or the view has more then you need. On top of this you can't use parameters.
You can create a table function that is like a SP but you call it like a table or view. And as a extra bonus you can use a cross/outer apply with a table function with a parameter and use a column from the table being connected to.
But if you have to create a SP and need to join the data you can always prefix a insert into infront of the exec command.
I would recommend when possible use with SCHEMABINDING to help with having a change brake your view or SP
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I rarely create views because when joining table you might have to join with table hints, or the view has more then you need. On top of this you can't use parameters.
You can create a table function that is like a SP but you call it like a table or view. And as a extra bonus you can use a cross/outer apply with a table function with a parameter and use a column from the table being connected to.
But if you have to create a SP and need to join the data you can always prefix a insert into infront of the exec command.
I would recommend when possible use with SCHEMABINDING to help with having a change brake your view or SP