Thanks. I understand your points. It is very clear. The objective is also to make tis DW GDPR compliant, and the encryption/decryption solution is fit for purpose. The GDPR aspects you mention are also part of the project. It is also true that the solution is more transaction oriented. But this is how SAS is being used at the moment in the company, for the project we are implementing. The users are given access to SAS Enterprise Guide to execute SQL queries they write themselves. This is the use case. So the use is transactional. The decryption must happen on a transaction basis, when data are returned encrypted to the users. (PS: having the data encrypted in the DW is a requirement. So having predefined decrypted view is not an option) I agree that it is better that decryption happens on the server side. In this case, do you think it is possible to have a generic approach based on modules, these modules calling the encryption/decryption APIs? I mean generic, because in this use case, every SQL queries are in scope, because they potentially embark sensitive data. Many thanks Gilles
... View more