Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %1!s! is missing underelement. Consider using an XML cursor plan captured from SQL Server without modification.
Current selection includes areas with the different types of markup. Select one of the options below to set a new markup ...
Current thread is not configured to access SQL Server internal resources and was likely created inside the Common Language ...
Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the ...
Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with ...
Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %1!s! is missing under element. Consider ...
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 procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements. ...