One common wait we may see (and not always a concern) is the wait type PAGEIOLATCH_EX. This can be a cause of a concern in some cases, as I note in Wait Types VII: PAGEIOLATCH_EX. Keep in mind that waits help us understand where we may have issues if we're seeing waits outside the normal pattern. If we're not regularly tracking these data for our environment, we may not have an idea of what has changed or where we may be seeing issues.
Some questions that are answered in the video:
- When may this be a possible concern?
- What do I mention about data to memory size?
- How does the type of environment possibly play into how we see this?
- What should we know about scaling operations and batching?
For mastering data transformation from one form to another form, check out the highest-rated Automating ETL course on Udemy. For a coupon to the course, check out the trailer video on the channel SQL In Six Minutes.
Fundamentally, troubleshooting waits should never override the basics. Provided that we have good prevention measures in place, these waits may only seldom point to issues. We should expect change over time, if our environment is changing over time.
Are you looking for tech consultants that can assist with design and development? From building custom applications to working with existing infrastructure that's causing you trouble, we can get you connected to consultants who can assist. You can contact for assistance.