Hi Hareen,

It is not a best practice to remove the blob from the work tables.

Probably, you can check with the size of the work page of each work objects. If it is too high, then you can optimize the size of the work page.

Some customers may flush or backup the older work objects data in equal interval of time to reduce the DB load. Check if it can be applicable for you.

Thanks.

You cannot separate the BLOB from the work table and this can not be implemented for any PRPC Application.

When ever a work object is saved in DB the following events occur in a sequence.

1. All the work object information is first stored in the blob.
2. Exposed table columns that require an update are identified.
3. Identified columns are populated with the latest data found in the blob.

Now its obvious why you cannot store the blob separately. As far as data is concerned everything revolves around the blob in PRPC.

To address the problem you have; try the following ...

1. Know the data retention policy of your client and purge any work object data that is older than expected number of months.
2. Place a partition in your DB tables for every 3 months. Discuss with your DBA on how this will help your application.
3. The size of the pyWorkPage should not exceed 5 MB; you could focus on staying within this limit. ( Usually a pyWorkPage will not grow beyond 100 KB. However in some applications the request and response XMLs of SOAP interactions are stored within the work object is such cases the pyWorkPage size could get out of control.)

Hi Hareen,

If Purging is not a solution to your requirement then the issue might resolve with partition of your DB table as said by Vignesh.

Please see link below, can pega function in normal way if the configuration in the link is implemented?

https://technet.microsoft.com/en-us/library/gg316768(v=sql.105).aspx