A database transaction log is expanding, even though the DBA is running log backups and doesn’t see an open transaction? What’s going on with this Availability Group?
I recently got an interesting question from a reader about running a CREATE INDEX statement with DROP_EXISTING
I’ve started up a weekly newsletter! Sign up, and each Tuesday you’ll get a link to a quick SQL Server quiz or poll in your inbox. Most weeks there will be a cartoon thrown in there, too.
SQL Server Management Studio is so full of tiny buttons and options that it can be easy to miss out on secrets that could make your life easier and more fun.
I’ve got a new online course that shows you my favorite secret tricks and goodies in SSMS!.
A few episodes ago, I talked about how learning about Write Ahead Logging was a light bulb moment for me, and helped me learn tons of concepts about backups and recovery.
This week, we talk about when SQL Server turns things upside down and doesn’t use write ahead logging: and what it has to do for recovery in these special cases.
I’ve never claimed to be great at math, but until recently I thought I knew how to count to one. Zero… one. That’s what we learned in kindergarten.
Apparently SQL Server didn’t go to kindergarten.
Last week I answered a set of fun interview questions from Mohammad Darab. One question that he asked really jumped out at me:
What are you most proud of doing/accomplishing for the SQL Server community so far in your career?
When you migrate a database, it can be useful to prove that you moved all the data and didn’t miss any transactions. Learn how to use a tail log backup in a migration scenario.
Here’s a great recent question that I got about query tuning and index use:
Assuming that the documented levels of data type precedence in SQL Server are true as of SQL 2016, why does a bigint value not force an index scan when compared against an int column?
Indexes help queries run faster in SQL Server for several reasons. One of those reasons is that indexes can help your update and delete statements lock fewer rows. And I’m not only talking about shared locks, either.
Copyright (c) 2024, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.
