Our company is currently experiencing an extreme spike in the 'DataverseSearch' Log capacity under our database usage table. The table grew by 10GB in the last 30 days.
While Microsoft recommends that the Dataverse is to be left on, we are noticing that this rapid growth is becoming an issue. Is there a way to reduce (e.g., deleting related logs) the capacity of the Dataverse Search table without loosing the search's functionality?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
5
Share
Report
All responses (
Answers (
