My learning is always fun. I strongly believe that unless you break something, you can’t learn how to fix them. While writing a new blog about auditing, I faced an interesting error. So, I thought of writing my findings before I write the actual blog. Let us learn about Audit failed to start Error 33222.
SQL SERVER – The Lease between Availability Group ‘PRODAG’ and the Windows Server Failover Cluster has Expired
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.
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 – Microsoft.SqlServer.Management.Sdk. Sfc.EnumeratorException: Failed to Retrieve Data for This Request
If you work with a product for a long time, you would start loving it. I have worked with many other RDBMS, but my love to SQL Server will never die. The amount of information available in logs is very helpful and can help in pointing the exact issue related to retrieve data.
SQL SERVER – Availability Group Missing or Deleted Automatically?
As a part of my passion, I try to help people in fixing simple issues and explain the behavior by looking at logs. Here is an email from my friend about Availability Group Missing or Deleted Automatically.
SQL SERVER – Maintenance Plan – Could not load type ‘Microsoft.SqlServer.Dts. Runtime.Wrapper. IDTSPackageSigning100’ from Assembly
One of my client was unable to modify the maintenance plan using SSMS. When we did various tests, we found that existing maintenance plans could execute and work. We tried creating a new maintenance plan and found it to be working. So, our issue is confined to “unable to modify existing plans”. Here is the error message