Skip to main content

SharePoint 2013 - Event ID: 8319

EventID: 8319

This is the error and this is the EVENT NAME
Table SqlIoData_Partition27 has 443957248 bytes that have exceeded the max bytes 442857142
Which is the SQL IO Usage event
To know the database name
Go to Central Admin 
First, we must get the logging database name
The database name is in this example
"WSS_Logging"

Now we need to find which table is taking most of the space inside the WSS logging Database.

You can check from the SQL Server
Login to SQL Server Management Studio -> Select your logging Database (Right Click) -> Reports- > Standard Reports -> Disk Usage by Top Tables
The SQL IO Usage event
We can reduce the retention period of any events (default is 14)
Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142
In my case its SQL IO
Any way if we couldn’t know exactly which identity is causing the problem we can just
Set them all to any number of days
Then log in the SharePoint power shell
Get-SPUsageDefinition
Set-SPUsageDefinition –Identity “Page Requests” -DaysRetained 3
Now I just changed the page Request to 3 days
Alternatively, you can set all the Identities once
By the following command
Get-SPUsageDefinition | Set-SPUsageDefinition -DaysRetained 3
After you are done
Run the two timer jobs to clean the old data ‘Microsoft SharePoint Foundation Usage Data Import’ and ‘Microsoft SharePoint Foundation Usage Data Processing’.
Go to Sharepoint Central Administration -> Monitoring -> Configure Usage and health data collection-> Log Collection Schedule.

Comments

Post a Comment

Popular posts from this blog

Forget SharePoint Adoption; Focus on Utilization!

SharePoint Adoption     Many SharePoint deployments stall or are never implemented throughout an organization.  These less than desired results are often use the excuse of a lack of SharePoint "adoption". Problems with "Adoption"      The whole idea of SharePoint "Adoption" implies a passive approach to rolling out a SharePoint deployment and a style of "build it and they will come" philosophy.  Generally, users, especially non-technical users, continue to do what they've always done out of habit or previous training.  Users will ONLY change their day-to-day tasks or tools if they are told to do so by their boss or if they're convinced a new tool or method can save them time or solve some obvious problem, such as daily tasks. Active Approach to drive Utilization      Any successful SharePoint deployment has to be proactively driven on a based on providing real and current solutions.  SharePoint deployments s...
Post a Comment
Read more
Automating Version History Trim in All Document Libraries in a SharePoint Online Site Collection Using PowerShell Managing version history in SharePoint Online is essential for maintaining an organized and efficient document library. By setting automatic version history trim, you can control the number of versions retained for each document, ensuring that your storage is used effectively and that users can easily access the most relevant versions. In this blog post, we'll walk you through the process of setting automatic version history trim on all document libraries in a SharePoint Online site collection using PowerShell. Why Set Automatic Version History Trim? Versioning in SharePoint Online allows you to track changes to documents and restore previous versions if needed. However, without proper management, versioning can lead to excessive storage consumption and cluttered document libraries. Setting automatic version history trim helps you: Optimize Storage : By limiting the num...
Post a Comment
Read more