We have a client .NET WPF application which connects to a local SQL 2008 Express server. We are using symmetric SQL encryption to encrypt some columns. In order to encrypt or decrypt, we must first open the symmetric key. We have a logon
trigger which opens the key automatically for us.
Unfortunately, the key is opened A LOT due to the key being closed after each session closes. This causes the CPU to peg at 100%. We are using connection pooling and it would be wonderful to have the key remain open across sessions. Anyone
have any thoughts on how to do this?
View Complete Post