WITH ENCRYPTION stored procedures cannot be edited
I have several encrypted stored procedures. The SSMS plugin is able to decrypt them so that I can submit them to source control, but I don't see a way to directly edit them from SSMS. My current solution is to create a local copy from subversion and checkout procedures from there and check them back in with my changes. Which makes me wonder why I need the RedGate plugin at all. I love that the RedGate plugin allows me to do all of my commits directly from SSMS and not have to use an external program.
I wish there was a context menu option to edit/modify the stored procedure.
-
Len Kalman commented
Sadly there is not an option to ignore the WITH ENCRYPTION parameter when performing a comparison.
This has been added the details of this support call to an existing feature request whose reference is SC-4419.
Just looking for more users who complain about this -
Len Kalman commented
I'm attempting to compare our development database vs a production database. When we deploy to production we set SQL Encryption on for all views, procedures, functions and triggers. With SQL Compare its showing that every view, procedure, function and trigger is modified, just because the production side has "WITH ENCRYPTION" for the objects. This forces us to manually evaluate the 1500+ objects that are encrypted to see if anything else has changed.