This one's for you, Paul! :-)
I have a customer which has two databases for two of his office locations. Both are roughly the same size (around 10 GB), both are hosted at the same professional hoster's site - so give or take, they're the same.
Yet, database A completes its
Check database integrity step in the maintenance plan in less than 30 minutes, while database B never even completes - the DBA killed the process after more than 3 hours of running.
These steps are being run "after hours" - so there shouldn't be any significant activity on the servers.
Any explanation? Any idea what to check for or where to look for a reason for this (and a way to solve it)? There are no error reported or anything.....