Let me state my position from the outset: Favoring AD Groups for security in SQL Server over individual AD Logins is a mistake. I don’t care what the “best practice” is. It’s a headache with no discernible advantage.
EDIT: I had two scenarios like this. The one written about here worked. The other one failed. The actual solution came from sql-ution.com. The solution is to fix the registry with the new value. And just in case his website comes offline before mine does, I'll post the code: Since I'm nostalgic for my wasted… Read More »
The trusty "sp_who2" is a quick way to look at what’s happening on your SQL instance, but completely lacks the ability to filter using a WHERE clause. You may have to manually sift through hundreds of results to find what you need. Never fear. This quick script gives you the same basic output that sp_who2… Read More »
When your security gets unruly, it can get time consuming to figure out how a user is accessing a SQL instance. Sometimes you may know that a user is getting access via one certain AD group but you aren’t sure if any other groups are granting access. Furthermore, a user might be in a group… Read More »
SSMS Boost is an add-on for SQL Server Management Studio. I used it for quite some time but I got tired of using it as freeware. The reason SSMSBoost as freeware didn't work for me was because they require that you continually re-download the new version and re-register every 120 days, otherwise it renders your existing… Read More »
So what happens when you run a query to check TempDB file sizes and SQL tells you that each file is 101 MB, but when you look in the file system, they’re actually a 45 GB each? Also, when you try to shrink the file, the shrink file dialog window shows free space as a… Read More »
Just a quick note on a scenario I ran into, and what I did to fix it: Scenario A user was running a stored procedure that created a table. Rather than having a table created in the "dbo" schema, it was creating a table with their user name as the schema, as in: DOMAIN\Username.TableName. The… Read More »
While this seems like a simple thing to do, I recently discovered so many ways not to do it (also known as failing) that I just had to document this one.
This is a bit of a scary task. Someone tells you about 87 databases that all need to be restored from the most recent FULL backups. You can either spend the rest of your day pointing and clicking, or you can use some PowerShell power to crank out the script and get on with your… Read More »
If you've painted yourself into the single_user corner, here is how you can get out.