We have recently upgraded a server from MSSQL 2008R2 Enterprise to MSSQL 2014 Enterprise. The one thing we didn't count on was a change to the database integrity checks. Using the exact same criteria and command, we have found that in 2008R2 a CHECKDB on all databases has gone from being a 1 hour task to a task that has run up to 18 hours and not completed. Our largest database is about 400GB, and running the same check on it now takes at least 4 1/2 hours to complete when ran on a low usage weekend. Has anyone else seen an increase in times when switching to 2014 for the CheckDB command? I am seeing at a minimum 4x the time for this one database, and if this is normal, we are going to have to look at a different way to do this.
↧