Query Store Entering Error State

Extremely rarely Query Store can end up in ERROR state because of internal errors or due to race condition when failover/restart happens while QDS cleanup running. Query Store can be recovered by executing sp_query_store_consistency_check stored procedure within the affected database. Please remember if QDS in ERROR state in that case it may affect Automatic plan… Read more

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

Msg 13575 OR Msg 13542 error message while adding period columns

You may see following error message while trying to enable system-versioned temporal table and adding period columns for a table which contain data: 1st error message: Msg 13575, Level 16, State 0, Line 32 ADD PERIOD FOR SYSTEM_TIME failed because table ‘temporaltest.dbo.CUSTOMERINFO’ contains records where end of period is not equal to MAX datetime. 2nd… Read more

SQL SERVER 2016 installation failing due to MSVCR120 missing Update (EXCEPTION_ILLEGAL_INSTRUCTION)

I was working on one of SQL SETUP issue with my colleague Shaurabh Thapa where in SQL SERVER 2016 installation was failing. So we looked into the setup logs and in detail.txt we could see following information:   Detail.txt (01) 2016-10-10 17:25:48 Slp: Sco: Returning service process id 0 (01) 2016-10-10 17:25:48 Slp: Configuration action… Read more

SSMS behaviour if you have Cluster Shared Volume and C drive repeating while choosing location for backup\restore\database attach

Consider this scenario, when you try to attach, restore or taking database backup using SQL SERVER Management Studio GUI and trying to choose the location then you may see C: drive repeating.   So this behavior may raise questions like, is it by design behavior? Will this cause any issue? Which drive to choose? So… Read more