DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, '%1!s!', '%2!s!' "and try again
DBCC SHRINKDATABASE for database ID %1!s! is waiting for the snapshot transaction with timestamp %2!s! and other snapshot ...
DBCC SHRINKDATABASE: File ID %1!s! of database ID %2!s! was skipped because the file does not have enough free space to reclaim. ...
DBCC SHRINKDATABASE: File ID %1!s! of database ID %2!s! was skipped because trying to adjust the space allocation for the ...
DBCC SHRINKFILE for file ID %1!s! is waiting for the snapshot transaction with timestamp %2!s! and other snapshot transactions ...
DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, ...
DDL replication is forcing reinitialization because either publication'%1!s!' uses character mode bcp, or timestamp/identity ...
Declarations do not match for parameter %1!s!. .NET Framework reference and T-SQL OUTPUT parameter declarations must match. ...
Decompression of data failed. Compressed data size: {0}. Expected decompressed data size: {1}. Actual decompressed data size: ...
Dedicated admin connection support was not started because of error 1!s!, status code: 2!s!. This error typically indicates ...