Query Store Best Practices for Mission Critical or Busy SQL Server

Query Store feature helping lot of SQL Admin in isolating top resource consuming queries quickly and also troubleshooting plan choice regressed scenario which is difficult to isolate or time consuming process. Now with powerful report and using few clicks you can check top resource consuming query and force optimum plan. In this article I would… Read more

Query Data Store Forced Plan behavior on AlwaysOn Readable Secondary

  We are getting following questions repeatedly from many customers so thought of writing a quick blog to explain the behavior. Question: For example if you have Query Data Store (QDS) enabled for user database participating in Always On Availability Groups and you Forced Plan for specific query, what happened if same query running on… Read more

Log Reader Agent Fail on Always On availability Groups configured on Multi-subnet

Recently I was working with one of Microsoft Partner on following issue wherein customer was migrating to SQL SERVER 2016 and during testing they have found Log Reader Agent was failing. I would like to share my learning from this issue and let me know if it is helpful or if you have any question. Consider… Read more

SQL SERVER Transactional and Merge Replication internal and work flow explained

Recently Sravani and I delivered session on SQL SERVER Transactional and Merge Replication and covered following topics: Different types of Replication in SQL Server Transaction replication work flow and troubleshooting latency – tips Merge replication workflow and troubleshooting agent failures Understanding Merge replication metadata Replication with SQL Server Availability groups Demos for replication issues You can… Read more

Troubleshoot 586 error message id with state 5 – The prepared statement handle 1 is not valid in this

Recently I worked with one of customer where in jTDS application getting an error 586 and in Profiler Trace we could see an exception with error message id : 586 State 5 with below text: The prepared statement handle 1 is not valid in this context.  Please verify that current database, user default schema, and ANSI_NULLS… Read more

Utility Control Point reporting incorrect CPU utilization when Server has more than 40 logical processor

Recently I have worked with one of customer wherein Utility Control Point (UCP) reporting incorrect CPU utilization when Server has more than 40 logical processor. So due to this issue customer getting false alert for CPU utilization, when CPU on Server below normal threshold. During troubleshooting we have found num_processors column of sysutility_mi_cpu_stage_internal table contain incorrect value…. Read more