We use certificate signatures on a handfull of stored procs that use dynamic SQL. The signature allows select/update access to the tables; otherwise users only have rights to execute the stored procedures. My problem is that these signatures do not get included in the synchronization scripts. I have identically named certificates across our servers, so I would like the "ADD SIGNATURE" statement generated in the synchronization script. Currently, unless I remember that a proc needs signing and manually sign the proc, the synchronization script succeeds but users receive an error message when they access that proc.
Comments
1 comment
-
Thanks for your post.
Add signature statements require certificates. Unfortunately we cannot really support certificates and asymmetric keys, because their content is inaccessible to SQL Compare via system tables. So consequently we cannot really do anything with the signatures either.
Add comment
Please sign in to leave a comment.