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.