I run a DBCC job that uses a cursor and does all DBCC checks on all databases in a server and writes the output to a txt file. Then I run on a daily basis a simple batch job, after the DBCC is run to check the DBCC output and e-mail me if any error messages are detected. I use the NT FINDRSTR command and a textual file as the input to it, that contain all the strings I am interested in. This list can be changed to suit individual requirements.
These jobs are run as scheduled jobs. They in fact can be also be run as a combined job. The zip file linked above contains two files.
For SQL Server 6.5
Author: R.Wimalaratne@iaea.org
Download Script:
searchdbcc.zip
Disclaimer: We hope that the information on these script pages is
valuable to you. Your use of the information contained in these pages,
however, is at your sole risk. All information on these pages is provided
“as -is”, without any warranty, whether express or implied, of its accuracy,
completeness, or fitness for a particular purpose…
Disclaimer Continued
Back to Database Journal Home
DatabaseJournal.com publishes relevant, up-to-date and pragmatic articles on the use of database hardware and management tools and serves as a forum for professional knowledge about proprietary, open source and cloud-based databases--foundational technology for all IT systems. We publish insightful articles about new products, best practices and trends; readers help each other out on various database questions and problems. Database management systems (DBMS) and database security processes are also key areas of focus at DatabaseJournal.com.
Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.
