DBCC CHECK cannot proceed on database %1!s! because it is a Secondary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CHECK. Reason may have been given in previous error.
Datepart - Is the parameter that specifies the part of the date to return. Some of the supported types are year(yy, yyyy), ...
DateTime kind needs to be explicitly set to either Local or Utc. The following DateTime value kind is unspecified: '{0}'. ...
DAX expressions that return Boolean values. Only rows that match the specified filters are visible to users in this role. ...
DBCC %1!s! is performing an exhaustive search of %2!s! indexes for possible inconsistencies. This is an informational message ...
DBCC CHECK cannot proceed on database %1!s! because it is a Secondary Replica and either Snapshot creation failed or the ...
DBCC CHECKCONSTRAINTS failed due to an internal query error. Please run DBCC CHECKDATABASE to ensure your data consistency. ...
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created ...
DBCC cross-rowset check failed for object '%1!s!' (object ID %2!s!) due to internal query error %3!s!, severity %4!s!, state ...
DBCC DBREINDEX failed because specifying FILLFACTOR is not allowed when creating or rebuilding a columnstore index. Rebuild ...