Link to home
Start Free TrialLog in
Avatar of imjamesw
imjamesw

asked on

Soft Deletion impact on server performance

Hi

I would like to know about Soft Deletions

I know how to set it up etc....
My question has to do with how it works

If i have a database that has several 1000 documents deleted each week would the overhead on the server be high
Each document would have a time stamp I would think, and then would the soft deletions be checked every hour within the time frame specified (48 hrs)to see what documents can now be permanently removed.


This could potentially be a high server use could it not.
On the otherhand if I have 1200 mail users with this feature turned on would that also be taxing on the resources to check every mail file once an hour for possible permanent deletions

Any advice or information welcome

Regards

James E Wood
Avatar of HemanthaKumar
HemanthaKumar

Follow this documentation

http://www-1.ibm.com/support/docview.wss?rs=899&uid=swg21091152


Database, advanced properties contain how many hours it has to retain soflt deletions

~Hemanth
Avatar of imjamesw

ASKER

Hi

I am looking for more architecture info
Severs demands and impact to the user or server
Yes it is always load on server.. You demand something from database to do.. implicitly you are asking server to do it..

I have seen soft deletions giving way to corruption of the dbs.. So beware of it
SOLUTION
Avatar of HemanthaKumar
HemanthaKumar

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
HemanthaKumar,
> I have seen soft deletions giving way to corruption of the dbs.. So beware of it

That was fixed years ago.  5.0.6 or 5.0.8, I think.
Thanx to All