AsyncOperation table in sandbox environment is unusually large

(0) Share

Report

Posted on by richard001

Hi all,

I copied our production environment to sandbox about a month ago and the AsyncOperation table in the sandbox is now unusually large. I've run through all the suggested system job bulk deletions but it is still massive - 28GB compared to under 6GB in production. Does anyone know if there is any more I can do to bring this down?

Thanks

All responses (4)

Answers (0)

kamay2 2 on at

Like (0)

Report

AsyncOperation table in sandbox environment is unusually large

Can you share what you found? I'm running into the same problem. Thanks!
richard001 32 on at

Like (0)

Report

RE: AsyncOperation table in sandbox environment is unusually large

I think I got to the bottom of this. Thank you!
richard001 32 on at

Like (0)

Report

RE: AsyncOperation table in sandbox environment is unusually large

Thanks for the tip, I'll take a look at this.

Also, I can confirm the sandbox is not in admin mode.

Richard
Suggested answer

PerezAguiar on at

Like (1)

Report

RE: AsyncOperation table in sandbox environment is unusually large

Hey Richard.

The first thing is that this is File capacity, not DB Capacity. There's a nice explanation on how to connect to the DB and understand why are those jobs there (in File Capacity) and checking since when. YOu can read it on .

Can you confirm that the Sandbox environment is running normally (i.e., doesn't have the "Admin mode" enabled? ) Also, by connecting to the DB and understanding what type of jobs are the ones being put on File Storage, you can understand better why this is not reducing.

Regards,