Did you enabled "Microsoft SharePoint Foundation Usage Data Processing " job as by default is "Disabled" as noted here: https://learn.microsoft.com/en-us/sharepoint/technical-reference/default-timer-jobs-in-sharepoint-server-2019

From the same link as above check to see if the "Microsoft SharePoint Foundation Usage Data Maintenance " and other "cleanup" jobs enabled by default runs as it should.

I would suggest you to check why the database is growing by finding which logs take most of the space and you can do that by following steps as described here https://petri.com/manage-wss_logging-database-sharepoint-2013/#:~:text=Because%20all%20of%20the%20logs,space%20on%20your%20SQL%20Server. and maybe adjust(reduce) the default 14 days retention OR reduce the amount of logging.

Hi,

I have found out that Request_Usage_Partition table, in WSS_Logging database is 300Gb and that is because this timer job is not working, so data is not purged as defined in Set-SPUsageDefinition -Identity "Page Requests" -DaysRetained 7. 

Manually purging is not solution as database will again be filled, so I would like to find out either why job is not working or, if it is possible, to create that specific timer job again.

On picture below, first timer job is working, second is not defined and third simple does not run (it is enabled). Even if you manually run it, it says that it has never run...

This is what I get regarding this timer job...

PS C:\Users\sp.admin> $TimerJobName="Microsoft SharePoint Foundation Usage Data Processing"

PS C:\Users\sp.admin> $TimerJob = Get-SPTimerJob | Where-Object { $_.displayname -like $TimerJobName }

PS C:\Users\sp.admin> Get-SPTimerJob $TimerJob | fl

DisplayName                 : Microsoft SharePoint Foundation Usage Data Processing

Description                 : Process and/or aggregate usage data in the logging database.

Service                     : SPUsageService

IsServiceJob                : True

WebApplication              :

Server                      :

LockType                    : Job

Schedule                    : daily between 03:00:00 and 05:00:00

Title                       : Microsoft SharePoint Foundation Usage Data Processing

LastRunTime                 : 1.1.0001. 00.00.00

Retry                       : False

IsDisabled                  : False

VerboseTracingEnabled       : False

HistoryEntries              : {}

EnableBackup                : False

DiskSizeRequired            : 0

CanSelectForBackup          : False

CanRenameOnRestore          : False

CanSelectForRestore         : False

Name                        : job-usage-log-file-processing

TypeName                    : Microsoft.SharePoint.Administration.SPUsageProcessingJobDefinition

Id                          : 5f5eb9dc-d36d-455e-96fd-b061787cd4b0

Status                      : Online

Parent                      : SPUsageService

Version                     : 17548725

DeploymentLocked            : False

Properties                  : {}

Farm                        : SPFarm Name=portal_SharePoint_Config

UpgradedPersistedProperties : {}

Manually purging is not solution as database will again be filled

In that case your options are: add more disk space to the location where WSS_Logging database is

OR

Lower the retention from default 14days to 3days or whatever fits on that volume.

Alternatively you should set the limit on that table only by following the steps described here:https://escalation78.rssing.com/chan-6524674/article31.html

Thing is, even if retention is 1 day, since job is not working it will not do anything. At this moment data in those tables is from Jun 2022, in stead of last 14 days.

Every solution requires that you run Microsoft SharePoint Foundation Usage Data Processing  timer job, which does not run for some reason.

I am trying to search ULS logs, but I am not proficient with it, so no luck atm :)

Here is how it looks in ULS: