SQL Server 2008 R2
- The function "%1!s!" does not support the data type "%2!s!" for parameter number %3!d!. The type of the parameter could not ...
- The function "%1!s!" requires %2!d! parameter, not %3!d! parameters. The function name was recognized, but the number of ...
- The function "%1!s!" requires %2!d! parameters, not %3!d! parameter. The function name was recognized, but the number of ...
- The function "%1!s!" requires %2!d! parameters, not %3!d! parameters. The function name was recognized, but the number of ...
- The function %{function/} takes an argument that evaluates to numbers or dates and cannot work with values of type %{datatype/}. ...
- The function LOG cannot operate on zero or negative values, and a zero or negative value was passed to the LOG function. ...
- The functionality you're trying to execute is disabled inside SQLCLR, if you still want to execute this functionality you ...
- The functions IsInNode or IsDescendant should be used only once and no OR operator should be used together at line %d{Line/}, ...
- The fuzzy lookup specified between input column "%1!s!" and reference column "%2!s!" is not valid because fuzzy joins are ...
- The Generate SQL Server Scripts Wizard allows you to generate scripts for databases and objects inside databases. This wizard ...
- The generated script file path '%1' has exceeded the length limit of %2!d! characters imposed by the Snapshot agent. Reducing ...
- The geometry index n ({0}) passed to STGeometryN is less than 1. The number must be greater than or equal to 1 and should ...
- The geometryType argument to InstanceOf ('{0}') is not valid. This argument must contain one of the following types: Geometry, ...
- The GetEnumerator method of the ForEach Enumerator has failed with error 1!8.8X! "%2!s!". This occurs when the ForEach Enumerator ...
- The given base allocator cannot be used by this delegating allocator because its page size is too small. The page size must ...
- The given inner allocator cannot be used by this small size allocator because its page size is too small. The page size must ...
- The given network name is unusable because there was a failure trying to determine if the network name is valid for use by ...
- The given XML instance is not valid because its top-level tag was {0}. The top-level element of the input Geographic Markup ...
- The Goal Seek tool provides useful recommendations when you know the desired value for a column of the current row (the Target ...
- The granularity attribute and intermediate granularity attribute should have same number of key columns (the granularity ...
- The granularity attribute has key column #{0} with data type '{1}' different than '{2}' from intermediate granularity attribute. ...
- The granularity attribute of the intermediate dimensions that are used to resolve many-to-many relationships should generally ...
- The graphical query designer is not available when connecting to a Microsoft SQL Server 2008 R2 data source using the Microsoft ...
- The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for column groupings ...
- The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in charts. ...
- The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in gauges. ...
- The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in maps. ...
- The grouping '{3}' in the {0} '{1}' has DataSet '{4}' as its domain scope. Only DataRegions and Grouping are allowed for ...
- The grouping '{3}' in the {0} '{1}' has {2} '{4}' and Parent defined. Domain scope is only allowed if Parent is not defined. ...
- The grouping '{3}' in the {0} '{1}' has {2} '{4}' with Parent defined. Grouping with parent defined cannot be a domain scope ...
- The hash value is not a one-dimensional array of bytes (error: %1!s!). This occurs in CPackage::LoadUserCertificateByHash. ...
- The Header or Footer is too complex to export to Word. Please group the ReportItems together into rectangles to simplify. ...
- The Health based load balancer did not find a healthy server to handle this request. Please add more resources to the farm. ...
- The heterogeneous log reader was unable to enter a tracer token into the distribution database: article ID = %1, publication ...
- The hidden field {0} is included in the query. Hidden fields cannot be hidden from the list browser when hidden fields are ...
- The hierarchy with ID of '%{hierarchyid/}', Name of '%{hierarchyname/}' referenced by the %{detaildimension/} measure group ...
- The hierarchy with ID of '%{hierarchyid/}', Name of '%{hierarchyname/}' referenced by the '%{cubedimension/}' cube dimension, ...
- The highest incompatible Management Data Warehouse version number "%s" is incorrectly formatted. Please contact your system ...
- The highest incompatible Management Data Warehouse version number "%s" stored in the configuration store is invalid. Please ...
- The Highlight Exceptions tool detects rows in your table that do not conform to the rules and generalizations that govern ...
- The highlighted volumes do not have enough disk space available for the currently selected features. You can remove files ...
- The HISTORIC_MODEL_COUNT parameter for the mining model, %{modelname/}, is not valid. The count must not be negative and ...
- The HISTORIC_MODEL_GAP parameter for the mining model, %{modelname/}, is not valid. The gap between the mining models must ...
- The History Cleanup task deletes historical data about Backup and Restore, SQL Server Agent, and Maintenance Plan operations. ...
- The History Cleanup task deletes historical data about Backup and Restore, SQL Server Agent, and Maintenance Plan operations. ...
- The history queue has reached maximum capacity before the history connection is set, the history connection should have been ...
- The HOLDOUT_PERCENTAGE parameter for the mining model, %{modelname/}, is not valid. HOLDOUT_PERCENTAGE must be greater than ...
- The ID property for the {0} is in the empty (or SMDL) namespace but it is not a GUID. IDs in the empty (or SMDL) namespace ...
- The ID, %1!lu!, is neither an input ID nor an output ID. The specified ID must be the input ID or the output ID that the ...
- The identifier '%1!s!' cannot be bound. Only source columns are allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement. ...
- The identifier '%1!s!' cannot be bound. Only target columns are allowed in the 'WHEN NOT MATCHED BY SOURCE' clause of a MERGE ...
- The identity property was attempted to be set for column %1!Iu!. Only columns of integer and numeric types can be marked ...
- The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure ...
- The ImpersonationInfo for datasource '%{Datasource/}' contains an ImpersonationMode that can only be used by a server administrator. ...
- The import population for database %1!s! (id: %2!s!), catalog %3!s! (id: %4!s!) is being cancelled because of a fatal error ...
- The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is ...
- The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors. ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
- The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...