Greetings. The object names used here reflect the article, though they were of course modified in my environment.
So I just completed the above exercise customized for our environment. I skipped the step of creating the sproc in db_source, because it already existed. However, when I would get to this part:
ADD SIGNATURE TO [schema_MyApp].[sp_MyApp01] BY CERTIFICATE [cert_MyAppSecIdentity]
WITH SIGNATURE = 0x5EF9C30476A8E3E248E9E11B7563528EB02DA1D8F440CAA9141841B9F3101F1988760D2775000CD0D70F44A8672984E327FBF2676E7FAC9AAED8E6F383A98B2A569A407577917E671F3D632EF7326AD3770A32E05CF43A613D310D64B6D52FD978E57A73912BF3587C475E48F4AA58561A7E0DB5D9DB53D35E03EC281BEC7772
I kept getting the message along the lines of "invalid public key". Of course I changed the sproc name and SIGNATURE according to my environment, so I don't know why there would be an issue? I only got around it when I dropped/ recreate the sproc in db_source,
which kind of has me worried.
View Complete Post