The status of association {0} could not be changed, because the current association status is incorrect. In order for the status to be changed to {1}, the current status of the association must be {2}.
The statement failed because column '%1!s!' (ID=%2!s!) uses collation %3!s!, which is not recognized by older client drivers. ...
The statement failed because the sql_variant value uses collation %1!s!, which is not recognized by older client drivers. ...
The statement is not supported on this version of the operating system. Could not find function entry point '%1!s!' in Httpapi.dll. ...
The statement, INSERT INTO . '%s{name/}'.CASES, is not valid when used with a mining model. This statement can be used only ...
The status of association {0} could not be changed, because the current association status is incorrect. In order for the ...
The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. ...
The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication ...
The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed ...
The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use ...