Fix for Event ID 8319 – Table that has exceeded the max bytes!

This error message flooded our event viewer.

There is no need to update the days how long the usage data will be kept or updating the sql data in order to expand the max bytes. That didn’t help me. In the internet i found several articles about that case, where people update the daysRetained property. I just helped a few hours. They used this script:

[code language=”csharp”]

Set-SPUsageDefinition -Identity “[name of definition]” -DaysRetained [number of days]

[/code]

What i did and what worked for me was to create a brand new usage data log database. The current will stay in the farm, but the usage data get a new database. This is so simple by just running this Powershell script:

[code language=”csharp”]

Add-PSSnapin Microsoft.SharePoint.PowerShell
Get-spusageapplication | Set-SPUsageApplication -DatabaseServer  -DatabaseName NewDatabaseName

[/code]

The current database for Usage logging will be kept in the database. I found the solution in this msdn blog article.

That’s it. The error should now keep staying away. So if you get an error like this one, just create a new logging database.

The article or information provided here represents completely my own personal view & thought. It is recommended to test the content or scripts of the site in the lab, before making use in the production environment & use it completely at your own risk. The articles, scripts, suggestions or tricks published on the site are provided AS-IS with no warranties or guarantees and confers no rights.

About Karsten Schneider 312 Articles
Consultant for Microsoft 365 Applications with a strong focus in Teams, SharePoint Online, OneDrive for Business as well as PowerPlatform with PowerApps, Flow and PowerBI. I provide Workshops for Governance & Security in Office 365 and Development of Solutions in the area of Collaboration and Teamwork based on Microsoft 365 and Azure Cloud Solutions. In his free time he tries to collect tipps and worthy experience in this blog.

Be the first to comment

Leave a Reply

Your email address will not be published.


*