A virtual event with 10 hours of informative sessions delivered across 2 days. The theme of the conference is The Data Debate.
Today I begin a week-long series where I will be discussing various SQL Server Monitoring Tools. My primary job is to help people with my consulting workshop Comprehensive Database Performance Health Check. While I help the customer with their various SQL Server performance issues, I often see my customers struggle with the monitoring their SQL Server’s health. One of the primary discussion at the end of consultation which we do is what tool is the best for their environment and how it can prevent them to walk into another trouble. Today we will talk about SQL Diagnostic Manager (SQLDM) in brief.
In administering SQL Server databases, the DBA is often presented with the task of identifying resource bottlenecks on the system and the sources of those bottlenecks. Also, the DBA is challenged with the task of identifying why specific queries take significant time to execute or affect the performance of other queries on the system. This allows the DBA to find opportunities to tune queries and improve their performance and the overall performance impact on the system. In this blog we will explore identifying if any disk I/O bottlenecks are present that impact query performance on the system. Such action would allow a DBA to further deal with the I/O bottleneck. Let us learn about Monitoring SQL Server.
As database administrators, we are constantly quizzed by our superiors to answer questions such as: how secure is our network, how secure is our data, is data secure at rest, is data secure in transition, who is accessing my data? All these are basic yet compelling queries businesses ask. In this age of competitive businesses, organizations are becoming tech savvy in building a secure fort for their critical data. Having worked on many projects in the past, these security measures are something I know are non-negotiable from an implementation point of view for administrators. When on this topic, I am reminded of a conversation about SQL Compliance Manager, I had with a junior DBA named Siva.