I just implemented TDE in our PeopleSoft HR databases with all PeopleSoft
tablespaces encrypted. No complaints from users, so the overhead appears to
be negligible.
On Thu, Feb 25, 2016 at 8:40 AM, Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:
Yep yep. Testing is a big priority for me. My recommendation is pushing
back on the business to identify what data objects are sensitive and we
move those objects and associated indexes to encrypted tablespaces.
Non-sensitive data (afaik) shouldn't need encrypting.
Thanks!
Chris
On Thu, Feb 25, 2016 at 8:32 AM, Hans Forbrich <fuzzy.graybeard@xxxxxxxxx>
wrote:
Yes. It is supported to have a mix of tablespaces within the same
instance. Note that Indexes are not forced to be on the 'same type' of
tablespace, so that could be cause for concern and additional
administration diligence.
Depending on the hardware, and depending on the encryption overhead it is
very reasonable to consider putting non-sensitive data in unencrypted
tablespaces. However, with modern hardware, possibly minimal and even
negligible impact is possible. As usual - test for yourself, within your
own environment.
/Hans
On 25/02/2016 6:54 AM, Chris Taylor wrote:
I think I know the answer to this question, but want to confirm for
completeness.
When you use Oracle TDE (with the appropriate licenses of course), is it
supported to have both non-encrypted tablespaces and encrypted tablespaces
in the same database, correct?
If it's not I'd be surprised but wanted to confirm.
Thanks!
Chris Taylor
