A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified in USE PLAN hint. First consider removing USE PLAN hint. Then if necessary consider (1) updating statistics, (2) using other hints such as join hints, index hints, or the OPTIMIZE FOR hint, (3) rewriting query or breaking it down into two or more separate queries.
A push subscription to the publication '%1!s!' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. ...
A query connection is unavailable or not supported for the requested query execution environment. This is usually due to ...
A query executing on %1 '%2' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge ...
A query fingerprint is the same for all queries of the same general form, even if the queries have different inline literal ...
A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified ...
A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the ...
A rate measure group must be related to a currency dimension (the dimension type must be Currency). No such measure group ...
A rate measure group must be related to a currency dimension. Either no currency dimension exists (dimension type must be ...
A read of the file '%1!s!' at offset %2!s! succeeded after failing %3!s! time(s) with error: %4!s!. Additional messages in ...