- Mais recentes
- Mais votos
- Mais comentários
The first step in any situation like this is your error logs. Assuming you have checked the error logs and found no errors that correlate with timing we then go on to the next step of checking wait statistics. By checking wait statistics, you can see the major symptoms of your issue. For example, if you see WRITELOG as your top wait statistic, then you know your issues are most likely related to transaction log write speed. If you were to see LCK_xx, then you know it's a locking problem.
To get started, begin with Wait Statistics advice from Paul Randal, the former team lead of the SQL Server Storage Engine - https://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/. It includes my favorite script for retrieving your SQL Server's wait statistics. Paul has numerous other resources there for you to take advantage of, such as a full library describing all of the wait stats and lots of great blog posts explaining them. Also, check out the blog post for the most worrying wait types - https://www.sqlskills.com/blogs/paul/worrying-wait-type/.
Of course, there are deeper symptoms and anti-patterns that feed the wait statistics. But to uncover those issues would require a full troubleshooting session.
Hope that helps you get started. Cheers, -Kevin
Conteúdo relevante
- AWS OFICIALAtualizada há 7 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos