Hi Manojt,
I agree with AmiBarrett on reducing the amount of data being logged to the DB will help tremendously. Plus depending on how the process runs it can actually dramatically improve performance. We had an old legacy process that used tons of loops and the run time went from hours to minutes to load a work queue.
However, its worth having specific notifications to monitor progress on key stages using the 'Work Queues' utility - 'Update Status' action. That way if you have mirror to the BP DB set you, you can query it and get detailed MI at any time.
Also in QA and Testing, logging everything can be useful for debugging. But agree 100% to limit logging in production.
@AmiBarrett
You proved the encryption is still in place? Could you tell me more about that?