Database Health Monitor – July 2016 Release
I have just released version 2.4.3 the July 2016 version of Database Health Monitor. You can download it now at the Database Health Monitor website.… Read More »Database Health Monitor – July 2016 Release
I have just released version 2.4.3 the July 2016 version of Database Health Monitor. You can download it now at the Database Health Monitor website.… Read More »Database Health Monitor – July 2016 Release
With previous versions of SQL Server to get the developer edition, it was usually available for around $50 USD at Amazon.com. With the introduction of… Read More »SQL Server 2016 Developer Edition
I am excited to announce that I have joined Carlos Chacon to become the co-host of the SQL Data Partners – SQL Server podcast. The weekly show has just reached 50 episodes, and Carlos has asked me to join him as co-host on the podcast.
In episode 50 Carlos introduces me as the co-host, the Corruption Compañero or the West Coast Compañero. I think I like the Corruption Compañero best. If you are a listener of the podcast you will recognize the word Compañero as companion, as in SQL Compañero or SQL companion. It’s a catchy term, and I am excited to be the Corruption Compañero on the podcast.
Today I released the latest update to Database Health Monitor. Version 2.4.2. It has been about a two weeks since version 2.4.1 release and version 2.4.2… Read More »Database Health Monitor Version 2.4.2 Released Today
Just one day after releasing Database Health Monitor version 2.4, today I released version 2.4.1. Version 2.4.1 includes a bug fix and 2 new feature that… Read More »Database Health Monitor Version 2.4.1 Released
If you haven’t tried Database Health Monitor Version 2.4 might be a good time to try it out. Five and a half years of my development time has gone into Database Health monitor, and hopefully the features will show it.
Here is what people have to say about Database Health Monitor.
Excellent – It’s the first tool I open every morning to see what is going on in my production environment! Thanks for the great work!
I personally used Database Health Monitor to manage over 100 instances of SQL Server, and it speeds up many of the daily maintenance checks.
Over the last several months I have added several new features, and many bug fixes. Here are some of the features and fixes included in this update.
Who owns that database? A quick check of the owner of most databases will likely reveal that the databases are either owned by sa, or… Read More »Database Owner? What user owns your database?
The question of how to delete a trigger after a specific date came up. Here is what could be done. If you want to… Read More »Drop a trigger after a specific date
Here is an error that popped up in the SQL Server error log today:
5/6/2016 10:10:10 AM spid22s Database [DatabaseName] has more than 10000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
Virtual Log Files (VLFs) are part of the SQL Server log file. When space is allocated in the log due to growth, that new chunk of log is broken up into Virtual Log Files
After looking further into this server, the VLF count turned out to be around 163,000. That is certainly the highest VLF that I have ever seen.
My personal threshold for too many VLFs is usually around 200 with my preference to be less than 100 VLF files. Others may have their preferences, they will all be far less than 10,000, and certainly less than the 163,000 that I had the opportunity to see today.
Updating SQL Server statistics may not be as obvious as it may sound.
Imagine this scenario. I invite you over for dinner and a game of Scrabble. After dinner, I start to do the dishes, while you set up the game. Rather than just doing the dishes that are dirty from our dinner, I decide to take all the dishes from the shelves, and drawers in my kitchen. I create a gigantic pile of all of the dishes, both clean and dirty on the kitchen counter. You get the game setup, and we start playing the game. Between turns, I jump back into the kitchen, and wash a few dishes, then on my turn, I jump back into the game and play my turn, then back to the kitchen again. During the game you are constantly waiting for me to jump back into the game to make my move. You could see how long this would draw out the game with me washing all the dishes, even the ones that were already clean. 4 hours later, I finally finish the dishes, and shortly thereafter we finish the game. It is unlikely, even if you love to play Scrabble that you would ever return to my house for dinner and a game again. Tomorrow night, when I have dinner with my family, I do the same thing, and every night after dinner I wash all the dishes in the kitchen, even the clean ones. You can see how wasteful this sounds, and perhaps some people would even label me as OCD or something worse in this scenario.
Although this is obviously the wrong way to do things, often times we end up doing the equivalent of this in our SQL Server maintenance tasks.