Check best practices

Hello Alex,

Thank you for reaching out to Yellowfin Support,

Yes, the fundamental guidance under the ReportInstance section of that Knowledge Base article remains valid and is still best practice for managing configuration database bloat caused by report execution logs.

However, when applying these steps on large production databases, there are crucial operational nuances to keep in mind-

1. Always take a full database backup prior to manual updates against the repository.

2. Stop Yellowfin or run during off-peak hours to avoid lock contention with active user sessions.

3. Execute deletions in chunks rather than a single large transaction.

Let me know if it helps.

Sincerely,

Nishant Garg

Yellowfin Technical Support Engineer

Hello Alex Flint

I wanted to follow up with you regarding the solution I provided in my last email. Did the solution we sent you resolve the issue?

Please let us know if you need additional support on this issue.

Thank you,

Nishant Garg

Yellowfin Technical Support

HI

Thank you for the follow-up, but no additional support is needed.

Regards,

Alex

Hello Alex Flint

I am glad to hear the issue was resolved. If you have any other issue please contact us again by opening up a new ticket and we will provide additional support.

You will be receiving a Survey to evaluate our support, it would be very helpful for us if you could hit us with a SATISFIED on that Survey.

Thank you,

Nishant Garg

Yellowfin Technical Support