Altering an INT Column to a BIGINT (Dear SQL DBA Episode 11)
You need to change an INT column to a BIGINT in a large table. Learn why this schema change can make your transaction log explode, and how to avoid it.
You need to change an INT column to a BIGINT in a large table. Learn why this schema change can make your transaction log explode, and how to avoid it.
You’ve got 99 problems, and the request coming in ain’t one.
Maybe you need to channel your inner Cat DBA, just for a moment.
SQL Saturday Oregon will be held on Oct 22, 2016 this year– the weekend before the SQL PASS Summit.
As a Portlander, I love it when people come visit my town! Please consider taking a few extra days to enjoy checking out PDX before or after the event.
What do you do when your fellow DBA is a ticking time-bomb of bad decisions, waiting to explode your production environment?
Psssttt – I have an updated blog post on this called the Learner’s Guide to SQL Server Performance Tuning
The SQL Server is slow, what should you do? I answer a reader question and share my strategy for performance troubleshooting.
In this episode of “Dear SQL DBA,” I answer a question about early adoption of SQL Server, discuss why testing in production isn’t necessarily crazy, and recommend how to handle requests to upgrade your SQL Server to use new features.
I’ve gotten a few compliments lately on the images I’ve been using in my posts. Images help engage your readers. You should also set a “featured image” for each post for thumbnail usage in your theme or in RSS readers. But it can be kind of a pain to search for images and make sure the image copyright allows you to use and share it.
Copyright (c) 2025, 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.