It isn't a complete record of every database write — only the areas of the app wired up to log to it show up here — but those areas alone can still generate a large volume of entries, including scheduled background jobs, which log under a name like "cron_<job name>" with a Run-type operation. Because of that volume, it's meant to be filtered down with the Tables/Operation/Users filters and search rather than browsed straight through. For a login- or permission-focused investigation, the dedicated System Logs screen is usually a better starting point.