Content-Type: |
text/plain; charset="us-ascii" |
Date: |
Wed, 11 Jan 2017 17:06:32 +0000 |
Reply-To: |
|
Subject: |
|
From: |
|
Content-Transfer-Encoding: |
8bit |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Sender: |
|
Parts/Attachments: |
|
|
If they are building retention into a from the ground up application, I would suggest that you add a retention that is very short. Two weeks, give it a try, if the information is gone than expand the timeframe. At least that should work in a POC.
Where it gets tricky is when tables with information have dependencies with other tables and those tables have information that has different retention requirements.
CALPINE CONFIDENTIALITY NOTICE:The information in this e-mail may be confidential and/or privileged and protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by mistransmission. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination, or copying of this e-mail and its attachments, if any, or the information contained herein is prohibited. If you have received this e-mail in error, please immediately notify the sender by return e-mail and delete this e-mail from your computer system. Thank you!
List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]
|
|
|