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 has a few new features, and a couple bug fixes. Here is a preview of the new logins report. First the logins panel on the Server overview report. When you click the overview panel, you …
Database Health Monitor Version 2.4.2 Released Today Read more »
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 were added after the release of version 2.4. Feature: Support for SQL Server 2016. Since SQL Server 2016 officially released yesterday, Database Health Monitor now supports SQL Server 2016. Bug: The check for the latest …
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 …
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 by someone with sysadmin permissions (or domain admin permissions). This is not recommended, however it is typically the case. It is generally recommended that the owner of a database be a user with limited permissions, certainly …
The question of how to delete a trigger after a specific date came up. Here is what could be done. If you want to trigger to disappear after a specific date or time, you can just drop the trigger from inside the trigger itself. Something like this. If instead of dropping the trigger you just want to disable it, …
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 …
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 …
After listening to an interview of Sean McCown (twitter) and some lively discussion on xp_cmdshell, I decided it would be a worthy enough discussion to create a blog post. At a minimum it might stir up some opinions. There are many varying opinions out there, including some really good opinions that applied to SQL Server 2000, but don’t really apply …
Please join Carlos and I for our first Database Corruption webcast on May 3rd. I have teamed up with Carlos and we will be presenting some thoughts on database corruption with an extended Q&A session. One important detail is we will be taking questions and answering them live on the webcast so this will be a great way to engage …
TL;DR summary: Don’t do it. Stop reading here if you want, but just don’t do it. This post refers to shrinking your database files (mdf, or ndf files), not shrinking the log file. The log file is a completely different conversation, however shrink database does shrink the log file. Not shrinking your database is one of the more counter intuitive …
DBCC ShrinkDatabase – I want to shrink my database. Read more »