> Your question isn't specific enough. What does "not compromised" mean?
Every technique for archiving records has some impact on some part of your
system. Is a 0.1% impact too
> much? A 1% impact? A 10% impact? A factor of 2 slowdown?
Sorry if my original question has not clearly conveyed
On Wed, Nov 21, 2012 at 1:21 AM, Gnanakumar wrote:
> Hi,
>
> Our application requirement demands archiving of records, so that
> performance/speed of the application is not compromised. So, am looking
> out/evaluating on various techniques/solutions available for database
> archiving, in general
