SSMS - modifying object right way and not via sp_executesql
We, database developers, are using SSMS for modifying objects like stored procedures daily. My routine is to list object in Object Explorer and click MODIFY. What I get is object definition wrapped with sp_executesql which is NOT SUITABLE FOR MODIFYING AT ALL!
Yes, I have „Check for object existence“ set to True in Options > SQL Server Object Explorer > Scripting. And I want to keep it like that.
This should not have anything in common with the act of modifying objects. The purpose of modifying is not to script things out but edit the object definition the most comfortable way.
Could you please change this behaviour to generate simple ALTER statetment WITHOUT sp_executesql?
This „feature“ is ruining my work!