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.
For SQL Server Emergency Help, you can reach out to me at pinal@sqlauthority.com with words URGENT in the email subject line for other services mention “Comprehensive Database Performance Health Check“.
Recently I got a message on Skype about SSMS.
Hi Pinal, Need quick suggestion. I am unable to find ssms.exe after installation of SQL Server. Do you know how I can install it?
Initially I thought that since SQL Server 2016 doesn’t come with SQL Server Management Studio, this would be an expected behavior. So, I shared my blog to him.
Question: How to Find Median in SQL Server?
One of my clients contacted me in assistance to install SQL Server. Generally, this is straightforward, but sometimes there are problems. This time we received an error message and it was very interesting. Let us learn about error related to the XML Document.
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.
I recently talked with Mark Wright, CTO of Nitrosphere, a company that optimizes SQL Server application performance. Let us talk about it.
“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.”
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