Development is a big undertaking and most of the time it focuses on making sure all the features are in place and working. Once this is done, tuning for performance often occurs. But in order to make adjustments, developers need data to understand where the issue is and then how to solve the problem.
Often, during application and database development, a significant workload of data and processes is not always in place to get a true understanding of how well the application will perform when you roll it out. So when you release the application, issues may come into play, such as blocking, deadlocks, timeouts, tempdb contention, and resource waits such as input/output, central processing unit, network, and more.
By using a tool like SQL Diagnostic Manager, data collection can occur all the time and when there is a need to analyze performance, all the data is accessible. In addition, by using the SQL Query Tuner add-on, you can get automated suggestions on how to change your code to make performance improvements.
There are several cases where developers can take advantage of the capabilities of SQL Diagnostic Manager. The main area is to find poor performing code, review query plans, and make adjustments. You could do this in production systems, of course. But you can also do this in development environments where you collect and review data to help you figure out what needs to be addressed. Other things developers may do is importing and exporting data from SQL Server. This could be another area that SQL Diagnostic Manager can monitor activity and help you find bottlenecks so you can make improvements.
For more information, please refer to the solution brief “Keep your SQL Servers running smoothly with SQL Diagnostic Manager” by Greg Robidoux from MSSQLTips.