SQL Server indexing basics are critical to query and server performance. Resources, like CPU and disk, are affected by the indexes that you have, or the ones you’re missing.
In the StackOverflow2013 database we’re going to look at Badges and users. Specifically, I want to start by seeing what badges a user has and when that user received them. Some badges, because of the type of badge it is, can be awarded more than once.
Query Store came out in SQL Server 2016. It was the next evolution of Microsoft’s attempts to provide valuable performance data. In this post you’re going to learn a bit about the history of native monitoring in SQL Server, why you should be using the Query Store, as well as how to view the information made available in SQL Server Query Store. This post is just an overview meant to get you to jump into using the feature. This feature is rich enough that someone can present on it easily for an entire day.
Teacher-Mentor-pexels-christina-morillo-1181398
What process can you use to find SQL Server training resources that will be valuable? After all, not everything on the internet can or should be trusted. If you want training on something in this constantly changing world of technology, how do you locate that training? How do you find information that is worth spending your time on? How much of it costs something? How much of it is free and is the free stuff any good?
Have you ever looked at sys.dm_os_virtual_file_stats and saw horrible latency for your database files? Generally speaking, you want to see latency below 20 ms on your database files. much above that and there are some problems somewhere that need some tuning.
But, how do you know what queries are causing your issue? What’s causing those IO waits?
I responded to a question on SQLServerCentral.com about performance that is related to these types of scenarios. The poster wanted to know if there was a way to correlate pending io requests with the queries that were experiencing the waits using the DMV sys.dm_io_pending_requests.