The logging database uses a separate partition table for the daily data for each category. For example, the timer job usage data for the first day is written to the dbo.TimerJobUsage_Partition0 table and the data for 32 days later is written to the dbo.TimerJobUsageUsage_Partition31 table.

Now each view give you the different information, i.e very time a user visit generates a page request, a record is inserted into one of the partitioned tables in this database and the “RequestUsage” view is kind enough to union all the data in the partitioned tables

Easy thing, you can run each view and you will see what information it return. You can create custom views as well.

https://www.codeproject.com/articles/70865/sharepoint-logging-database

https://technet.microsoft.com/en-us/library/hh769360(v=office.14).aspx#section2

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Waqas Sarwar9y ago
Accepted answer
The logging database uses a separate partition table for the daily data for each category. For example, the timer job usage data for the first day is written to the dbo.TimerJobUsage_Partition0 table and the data for 32 days later is written to the dbo.TimerJobUsageUsage_Partition31 table.

Now each view give you the different information, i.e very time a user visit generates a page request, a record is inserted into one of the partitioned tables in this database and the “RequestUsage” view is kind enough to union all the data in the partitioned tables

Easy thing, you can run each view and you will see what information it return. You can create custom views as well.
https://www.codeproject.com/articles/70865/sharepoint-logging-database

https://technet.microsoft.com/en-us/library/hh769360(v=office.14).aspx#section2

Details on SP 2013 Database Views in WSS_Logging database

https://www.codeproject.com/articles/70865/sharepoint-logging-database