sql server - SQL 2016 Always Encrypted columns and SQL temporary tables (#temp) -


we looking solution implement "always encrypted" columns in database, using @ same time many sql temporary tables (#tmp).

we explored alternate path - stop using #temp tables, mean high impact on our app in terms of time/cost.

did find way write queries "insert #tmp select my_table", my_table contains ae columns?

i tried applying same cmk , cek tempdb database, can create same structure #tmp table, structure of my_table. doesn't solve problem though - having tables in 2 different databases seems prevent data transfer.

i'm looking sql solution, , not solution involves client app (c#, vb, etc.) has access encryption keys.

insert operations in manner describing not supported encrypted columns.

"insert #tmp select my_table"

you have write client app achieve similar result. if want explore path, please leave comment , can guide you.


you should able achieve similar in c# follows.

  • do select * encryptedtable load data in sqldatareader use sqlbulkcopy load temp table using sqlbulkcopy.writetoserver(idatareader) method

if have encrypted table , plaintext table on same sql server instance, aware might leaking information sql server admin, because can examine plaintext data , corresponding ciphertext


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -