To build the answer that @PhillipH provided: if you do an exact search by (say) last name, you can include a computed column defined as CHECKSUM(encrypt(last_name))(using encryptyour encryption operation). This is safe in that it does not divulge any information - the checksum of the encrypted value does not report anything in plain text.
. , , WHERE encrypted_last_name = encrypt(last_name), : WHERE encrypted_last_name = encrypt(last_name) AND CHECKSUM(encrypt(last_name)) = hashed_encrypted_last_name. , SQL Server , , , . , CHECKSUM - . , / ( , , ), , .
, , , . ( encrypted(TOUPPER(name)), , , ), . , , - , Lucene, , (.. (EFS) Windows). , , , - , SQL Server .
/ , (TDE), , SQL Server . , , ( ), , , . , TDE .