SQL Server has incredibly verbose error logs, and sifting through them for the highlight reel can be a pain. They’re often full of messages that you aren’t actionable.
- Failed logins
- Successful logins
- Successful backups
Making matters worse is that when you open large log files, the response time for loading all those messages can be painful, and even time out.
But Erik has a nice stored procedure to filter out the chaff. Read on to learn more about it.