This is one of the common errors I have seen while working with customers who are using SQL Server AlwaysOn availability groups. Once this error comes, the resource in the cluster goes to failed state and in SQL Server Management Studio, we should be an availability group in resolving state. Resolving state essentially means that the role of availability group is neither primary nor secondary.
What is the Difference between SUSPECT and RECOVERY PENDING? – Interview Question of the Week #114
Question: What is the Difference between SUSPECT and RECOVERY PENDING?
SQL SERVER – Could Not Use View or Function ‘msdb.dbo.sysdac_instances’ Because of Binding Errors
SQL SERVER – Could Not Use View or Function ‘msdb.dbo.sysdac_instances’ Because of Binding Errors. Let us learn how to fix the error.
SQL SERVER – Jump in Identity Column After Restart
The SQL Product team makes a continuous change in the product which sometimes causes unpredictable behaviors in the SQL Server engine. One of such change was done in SQL Server 2012 which caused the behavior which I just said in the subject line Identity Column.
SQL SERVER – AlwaysOn Listener Error – The WSFC Cluster Could Not Bring the Network Name Resource With DNS Name ‘DNS name’ Online
I can tell you how many times I have heard about this error. This can appear in any of the situation where SQL needs to create a cluster network name resource in the WSFC Cluster. Here are the two situations I can think of:
Installing SQL Server Failover Cluster instance.
Creating listener in the AlwaysOn availability group.
SQL SERVER – 10 Questions Where YES May Be a Wrong Answer – Performance Health Check
Today’s blog post created from a recent conversation with one of my customers. They asked me a very interesting question – “When should they hire me for my famous Comprehensive Database Performance Health Check?”. I send them following 10 questions and told them to take a quick quiz about their SQL Server Environment. They replied back to with YES to all the answers. If the answer to any of the following questions in YES, that means user can for sure improve your SQL Server’s Performance. After taking this quick test, my customer realized that they have amazing potential to improve the performance of their server.
SQL SERVER – DBCC SHRINKFILE: Page 1:26423878 Could not be Moved Because it is a Work Table Page – TempDB Files
This blog is an outcome of an email communication with my client. The issue was that they were having big tempdb files. They had multiple files and of uneven size. As soon as they restart SQL, the initial size itself was huge and when they tried to shrink the TempDB database, it was not doing anything. Here was the message in SQL Server Management Studio query window.