2026-07-27
504 reads
2026-07-27
504 reads
2026-07-13
683 reads
2026-06-30 (first published: 2026-06-29)
1,391 reads
2025-11-10
1,061 reads
2025-11-03
1,313 reads
In my last post, I talked about how you can get 43%-67% faster backups. This time, I’m using that same SQL Server setup to discuss how throwing more CPU cores might help you check for corruption faster if you’ve already got modern fast storage.
2020-09-28
Introduction A popular joke about DBAs and database backups goes like this. There are two types of DBAs: DBAs that do backups DBAs that will do backups The joke is only stating the obvious – lack of database backups might be the end of a DBA career and/or the supported business. Unfortunately, that joke fails […]
2020-01-07
10,355 reads
In this tip we look at to create a SQL Server DBCC CHECKDB errors email formatted in an HTML table. This will report any errors for all of your databases on the server.
2018-10-24
2,764 reads
The SQL Server model database is one of the core system databases, but it seem to get less attention in terms of importance. This post from Simon Liew will demonstrate the havoc the model database can cause when database integrity checks exclude the model database and corruption goes undetected.
2017-01-26
4,940 reads
DBCC CHECKDB is a built-in SQL Server command that allows you to check database integrity and consistency in one simple command, but running it on large databases can be a nightmare. In this article, Ahmad Yaseen explains how you can enhance the command to run faster in SQL Server 2016.
2016-09-28
3,423 reads
By Steve Jones
Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...
By Steve Jones
I was creating a question on sp_readerrorlog and realized that this procedure is different...
By SQLPals
Why sys.fn_dblog Is Undocumented And Why It's Still There Why sys.fn_dblog...
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
Comments posted to this topic are about the item The Disabled Index
Comments posted to this topic are about the item Server-Level Table sizes
I run this code on SQL Server 2022.
CREATE TABLE Drink
(
drinkid INT NOT NULL
CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
drinkname VARCHAR(20),
rating NUMERIC(2, 1)
)
GO
INSERT INTO Drink
(
drinkid,
drinkname,
rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result? See possible answers