“How come my database is only a few MBs big and I am facing performance problems?” My customer asked. I replied, “Well, this is because you are not running job using SQL Server Agent to keep your indexes in the best health.”
SQL SERVER – Huge Size of Table catalog.execution_component_phases in SSISDB
Have you ever faced a situation where the table size in SSISDB is very huge? Are you are wondering what this SSISDB database is? It has information about the SSIS catalog execution and we should not truncate them as they belong to SSIS subsystem. Once I faced a situation where I could see SSISDB was very huge in size. When looking for more help, I found under the MSDN link which talks about the table. https://docs.microsoft.com/en-us/sql/integration-services/system-views/catalog-execution-component-phases?redirectedfrom=MSDN&view=sql-server-ver15
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.
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.
Is your SQL Server running slow and you want to speed it up without sharing server credentials? In my Comprehensive Database Performance Health Check, we can work together remotely and resolve your biggest performance troublemakers in less than 4 hours.
Once you learn my business secrets, you will fix the majority of problems in the future.
Have you ever opened any PowerPoint deck when you face SQL Server Performance Tuning emergencies? SQL Server Performance Tuning Practical Workshop is my MOST popular training with no PowerPoint presentations and 100% practical demonstrations.
Essentially I share my business secrets to optimize SQL Server performance.