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,114 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
An enhanced version of a script originally posted by Robert Pearl some time ago. It now takes into account changes in the tabelresults for CHECKDB in latter versions of SQL Server.
2016-05-04 (first published: 2016-04-20)
1,256 reads
Sometimes running DBCC CHECKDB WITH DATA_PURITY returns thousands of affected columns. This script automates the identification of those columns.
2015-04-13 (first published: 2013-07-04)
2,417 reads
This article describes a utility that is able to report the most common DBCC CHECKDB errors significantly faster than DBCC CHECKDB does itself.
2011-08-23
15,339 reads
Ever restored a corrupted database from the backup, only to find that the backups are corrupted too - All the backups? Sure it can happen and it isn't nice when it does. To check that a database backup is internally consistent you have to use DBCC CheckDB. On a huge highly-loaded live system? Grant Fritchey has, as usual, a practical solution.
2011-05-02
3,896 reads
2009-09-17
5,021 reads
By Steve Jones
I’m starting a long trip at Boston this weekend. I’ll be there Saturday speaking,...
As a data & AI strategist who’s seen countless projects succeed and fail, I...
By SQLPals
Set Theory vs. Batch Mode in SQL Server Not long ago,...
Comments posted to this topic are about the item Changing the Recovery Time
Comments posted to this topic are about the item Getting More Time from AI
Comments posted to this topic are about the item When Page Prefetching Takes a...
I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means?
ALTER DATABASE Finance SET TARGET_RECOVERY_TIME = 12 xxx;See possible answers