Request for feedback: SQL Server encryption interoperability on MSDN forums
You may be aware that the native encryption is introduced in SQL Server 2005 by making use of the algorithm involves a component known as the encryption key (a sequence of characters).
Using this method the process can be reversed by applying an appropriate decryption key and equivalent algorithm, yielding the original data. The keys forming the pair used in asymmetric algorithms are known as public and private.
SQL Server Development Team (Security) has been reviewing the methods and interoperatbility between SQL Server encryption and CLR, in this regard they are looking for a feedback from the users.
If you are using encryption within SQL Server or using CLR encryption (CAPI) then make sure to let your feedback over here.
All these has been started from another MSDN thread as a reference.