Only %1!s! out of %2!s! rows were updated in the batched update procedure for table %3!s!; other rows could not be updated because they have been deleted. No action is required, but if this condition occurs frequently, determine if update-delete conflicts can be avoided. Batch updates can be helpful for performance.
One row in this grid represents statistics for all plans with a given plan_fingerprint value. This is a statement_end_offset ...
One row in this grid represents statistics for all plans with a given plan_fingerprint value. This is a statement_start_offset ...
One-to-many: Facts are recorded in one currency. The conversion is applied at the cube level with multiple target currencies. ...
Online addition of CPU resources cannot be completed. A software non-uniform memory access (soft-NUMA) configuration was ...
Only %1!s! out of %2!s! rows were updated in the batched update procedure for table %3!s!; other rows could not be updated ...
Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows ...
Only a constant expression is allowed for the '%{ArgumentIndex/}' argument of the function '%{FunctionName/}' at line %d{Line/}, ...
Only a constant expression that returns a positive number is allowed in the third argument of a Top or Bottom function. The ...
Only a nested table column with a KEY column inside is allowed in an association prediction function. See line %d{Line/}, ...