Custom parameter layout was removed from the report. SQL Server 2014 Reporting Services and earlier do not support custom parameter layout.
Cursor plan forcing failed because input plan has more than one node with OperationType=%1!s!. Consider using an XML cursor ...
Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch. ...
Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, ...
Custom parameter layout was detected in the report. SQL Server 2014 Reporting Services and earlier do not support custom ...
Custom parameter layout was removed from the report. SQL Server 2014 Reporting Services and earlier do not support custom ...
Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements. ...
CUSTOMDATA and USERNAME functions are not supported in calculated columns. These functions may only be used in Measures or ...
Cyclical forwarding detected for event %1: Event source was '%2' which matches the current forwarding server. The event was ...
Cyrillic-General-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...