SQL Server 2012

  1. The JoinType custom property for the %1!s! contains a value of %2!ld!, which is not valid. Valid values are 0 (full), 1 (left), ...
  2. The JoinType property specified for input column '%1!s!' differs from the JoinType specified for the corresponding reference ...
  3. The key attribute of the %{dimension/} data mining dimension does not have the required, related attribute named ATTRIBUTE_NAME. ...
  4. The key columns of the %{detailproperty/} measure group attribute do not match in either number or data types to the key ...
  5. The key columns of the '%{parentproperty/}' parent attribute must have the same composition and data types as those of the ...
  6. The key constraint '{0}.{1}.{2}' will not be scripted as an index for article '{3}' because it references a user-defined ...
  7. The key constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it references a user-defined type column ...
  8. The Knowledge Base contains unpublished knowledge from previous process. Changing data source mapping will cause losing this ...
  9. The Knowledge Base contains unpublished matching policy. Changing the data source mapping will cause all this data to be ...
  10. The Knowledge Base contains unsaved analysis data from the last analyze operation. Running the analyze operation will cause ...
  11. The Knowledge Base contains unsaved analysis data from the last analyze operation. Running the analyze operation will cause ...
  12. The knowledge base that is used for this project has been updated with new published knowledge. However, there are conflicts ...
  13. The knowledge base that is used for this project has been updated with new published knowledge. Would you like to use the ...
  14. The label {0} in the input well-known text (WKT) is not valid. Valid labels are POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, ...
  15. The language of SQL Server instance {2} does not match the language expected by the SQL Server update. The installed SQL ...
  16. The language of the original media does not match the language of the service pack. Either SQL Server Product Update discovered ...
  17. The last row in the sampled data is incomplete. The column or the row delimiter may be missing or the text is qualified incorrectly. ...
  18. The layer wizard cannot run because the value for the layer DataSetName property is blank. Specify a valid dataset name and ...
  19. The layer wizard cannot run because the value for the spatial data DataSetName property is an expression. Expressions are ...
  20. The layer wizard cannot run because the value for the spatial data DataSetName property is blank. Specify a valid dataset ...
  21. The layer wizard cannot run because the value for the spatial data DataSetName property is not valid. Specify a valid dataset ...
  22. The layer wizard cannot run because the value for the spatial data Source property is an expression. Expressions are not ...
  23. The layer wizard cannot run because the value for the spatial data Source property is blank. Specify a valid file source ...
  24. The lease between availability group '%1!s!' and the Windows Server Failover Cluster has expired. A connectivity issue occurred ...
  25. The length %1!d! is not valid for function "%2!s!". The length parameter cannot be negative. Change the length parameter ...
  26. The length (%1!Iu!) provided for a text/ntext/image column of a Table-Valued Parameter Rowset exceeded the SQL Server limit ...
  27. The length of input column '%1!s!' is not equal to the length of the reference column '%2!s!' that it is being matched against. ...
  28. The length of string column '%1!s!' exceeds 4000 characters. A conversion from DT_STR to DT_WSTR is necessary, so a truncation ...
  29. The length of the private key for the security certificate bound to database principal (Id: %1!s!) is incompatible with the ...
  30. The length of the public key for the security certificate bound to database principal (Id: %1!s!) is incompatible with the ...
  31. The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error. ...
  32. The length ~0 was specified for type "%1" for column %2!Iu!. ~0 is only a valid length for varchar(max)/nvarchar(max)/binary(max) ...
  33. The lengths of parameter names, types, and descriptions arrays are not equal. The lengths must be equal. This occurs when ...
  34. The level of the index. Level 0 is the leaf (or data) level of the index. Level number increases moving up the tree toward ...
  35. The level with ID of '%{levelid/}', Name of '%{levelname/}' referenced by the '%{cubehierarchy/}' cube hierarchy does not ...
  36. The license for the installation of SQL Server on '{0}' permits the server to use only itself as a Distributor. Refer to ...
  37. The license for this installation of SQL Server does not permit the creation of transactional publications. Refer to your ...
  38. The lineage ID of the output column that will receive the value from this input column. Or -1 if column's value is not used ...
  39. The lineage identifier of an input column that contains a PivotedValue or the value -1. The value -1 indicates the column ...
  40. The linearRing input is not valid because there are not enough points in the input. A linearRing must have at least 4 points, ...
  41. The Linguistics property is specified for the {0}, but the Name property is omitted. Linguistics cannot be specified for ...
  42. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because it contains MG dimension ...
  43. The linked %{typename/} with the ID of '%{id/}', Name of '%{name/}' cannot be processed because its source object is not ...
  44. The list below shows which objects will be affected by the processing task. To process an object, select its check box. Selected ...
  45. The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %1!s! pages were ...
  46. The listener for the WSFC resource '%1!s!' failed to start, and returned error code %2!s!, '%3!s!'. For more information ...
  47. The listener is not configured for the availability group. Either configure the listener now on the Specify Replicas page, ...
  48. The listener with DNS name '%1!s!' does not conform to SQL Server listener guidelines, and cannot be configured through SQL ...
  49. The listener with DNS name '%1!s!' for the availability group '%2!s!' is already listening on the TCP port %3!s!. Please ...
  50. The LoadFromSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  51. The local availability replica of availability group '%1!s!' cannot accept signal '%2!s!' in its current replica role, '%3!s!', ...
  52. The local availability replica of availability group '%1!s!' cannot become the primary replica. The last-known primary availability ...
  53. The local availability replica of availability group '%1!s!' did not become primary. A concurrent operation may have changed ...
  54. The local availability replica of availability group '%1!s!' is in a failed state. The replica failed to read or update the ...
  55. The local computer is an owner of a cluster group that contains the SQL Server service, Analysis Services service or a generic ...
  56. The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server ...
  57. The local computer is the only node left in the failover cluster that has not been upgraded, or it is a single-node failover ...
  58. The local connection is not available. This typically occurs because the AdomdServer object model is not being used within ...
  59. The local data source '{0}' contains a connection string that is an expression and cannot be converted to a shared data source. ...
  60. The local node is not part of quorum and is therefore unable to process this operation. This may be due to one of the following ...
  61. The local node is not part of quorum and is unable to initiate a failover. This could be caused by one of the following reasons: ...
  62. The local node is not part of quorum. This could be caused by one of the following reasons: The local node is not able to ...
  63. The local node of the failover cluster has already been upgraded, and no other nodes have been upgraded. It is not possible ...
  64. The local partition map for database %1!s! is starting up in reduced functionality mode because of log full. Pending partition ...
  65. The local service account is different from the active node. Use the SQL Configuration Manager to change the service account ...
  66. The localized description given in the {0} element which defined the {1} package could not be loaded, refer to the inner ...
  67. The location for temporary storage of buffer data. You can specify multiple directories by using semicolons to delimit the ...
  68. The location for temporary storage of columns that contain binary large object (BLOB) data. You can specify multiple directories ...
  69. The location of the gauge image inside the gauge container. The coordinates are measured as a percentage of the container's ...
  70. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width ...
  71. The location of the gauge inside the gauge container. The coordinates are measured as a percentage of the container's width/height. ...
  72. The location of the gauge label inside the gauge container. The coordinates are measured as a percentage of the container's ...
  73. The location of the indicator inside the gauge container. The coordinates are measured as a percentage of the container's ...
  74. The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred ...
  75. The log configuration has been changed by another user, Your changes cannot be saved. The new settings are about to be loaded. ...