Log job output to file - information missing? dbcc checkdb

Question

Hello
Not sure where to put this question.. feel free to move it if necessary.
I have a job which runs DBCC CHECKDB WITH PHYSICAL_ONLY on every database on the instance which is read_write. Problem is that I want to get the output of the result to make sure that every database is actually performing this command. When viewing normal
history by right clicking the job and select "view history" I get cut off information due to the lack of space allowed (1000 chars default I think).
So I tried to log it to table and view it by msdb.dbo.sp_help_jobsteplog but the information here does not cover all databases as well.. So then I tried to log it to a file. But I get the same information there, and not all databases are logged.
So I start to wonder if the dbcc checkdb job does not get executed on the other databases?? If I look in the Current SQL Server Logs I only see that DBCC CHECKDB WITH PHYSICAL_ONLY executed on the same databases that is listed in my output file.
What can I do? the instance contains over 400 databases but only approximately 70 is logged as doing a dbcc checkdb.
This is my command:
SET NOCOUNT ON
EXEC sp_MSforeachdb @command1='
IF NOT(SELECT DATABASEPROPERTYEX(''?'',''Updateability''))=''READ_ONLY''
BEGIN
DBCC CHECKDB (?) WITH PHYSICAL_ONLY
END'

Answer 1

There is a known issue with sp_MSforeachdb where under heavy load the procedure can actually miss databases with no errors. That can be the case in your environment. Aaron Bertrand wrote about the issue and solutions for the problems in the article:
Making a more reliable and flexible sp_MSforeachdb.
Ana Mihalj