SQL Server 2008

  1. The 'schema_option' property for a merge article cannot be changed after a snapshot is generated for the publication. To ...
  2. The 'status' value must be 'no column names', 'include column names', 'string literals', 'parameters', 'DTS horizontal partitions' ...
  3. The '{0}' #{1} has NullProcessing set to 'UnknownMember', but the dimension doesn't have UnknownMember set to 'Visible' or ...
  4. The '{0}' and '{1}' measure groups have the same dimensionality and granularity. Consider unifying them to improve performance. ...
  5. The '{0}' attribute is used to relate this dimension to the '{1}' measure group in the '{2}' cube. Please review this relationship ...
  6. The '{0}' attribute is used to relate this dimension to {1}. Please review these relationships in the Dimension Usage tab ...
  7. The '{0}' column is used in the data relationship between the case and the nested table. It usually does not contribute useful ...
  8. The '{0}' cube could not be retrieved from the server. Verify that the server is running and that the cube is processed. ...
  9. The '{0}' database already exists on the '{1}' server. If you proceed with deployment, the database will be overwritten. ...
  10. The '{0}' database on '{1}' has changed since the last time the project was deployed. If you proceed with deployment, the ...
  11. The '{0}' default measure, that was defined on the perspective or inherited from the cube, is not included in the perspective. ...
  12. The '{0}' dimension cannot be used unless one of the following tables is included in a new dimension: {1}. Either select ...
  13. The '{0}' dimension cannot be used unless the '{1}' table is included in a new dimension. Either select the '{1}' table or ...
  14. The '{0}' dimension must be used by all measure groups that use the account dimension. Select another dimension or ensure ...
  15. The '{0}' dimension should use MOLAP storage mode because the measure group contains semi-additive measures. Also, if proactive ...
  16. The '{0}' entity represents a dimension. Therefore, the identifying fields for this entity must belong to the same entity. ...
  17. The '{0}' entity represents a measure group only. Therefore, the identifying fields for this entity must belong to entities ...
  18. The '{0}' granularity attribute from the '{1}' time dimension should have its AggregationUsage property set to '{2}' because ...
  19. The '{0}' mining model has been changed and the data mining query you have built is no longer valid. Do you wish to start ...
  20. The '{0}' mining model has been deleted and the data mining query you have built is no longer valid. Select a different mining ...
  21. The '{0}' mining model must be processed before you can browse its content. It could take some time to process the mining ...
  22. The '{0}' mining structure does not include a test set. You need a test set to create a classification matrix. Create a test ...
  23. The '{0}' mining structure does not include a test set. You need a test set to create an accuracy chart. Create a test set ...
  24. The '{0}' mining structure has already been processed. Are you sure you want to re-process the mining structure and all the ...
  25. The '{0}' object '{1}.{2}.{3}' may not be replicated successfully because it references the object '{4}.{5}' which is not ...
  26. The '{0}' object '{1}.{2}.{3}' will not be scripted for article '{4}' because it references the object '{5}.{6}' which is ...
  27. The '{0}' object '{1}.{2}.{3}' will not be scripted for article '{4}' because it references the unpublished object '{5}.{6}'. ...
  28. The '{0}' parameter cannot be null, the empty string, or a string consists solely of blank spaces if standard security is ...
  29. The '{0}' parameter must have a value of 'dbnmpntw'(Named Pipes), 'dbmsrpcn'(Multiprotocol), 'dbmsadsn'(Apple Talk), 'dbmsgnet'(VIA), ...
  30. The '{0}' property has NullProcessing set to 'UnknownMember', but this is only allowed on KeyColumns of dimension attributes ...
  31. The '{0}' table cannot be used as a nested table because it does not have a many-to-one relationship with the case table. ...
  32. The '{0}' table is currently used by the '{1}' partition, and you have not supplied a query to restrict its rows. Measure ...
  33. The '{1}' algorithm does not support the content type contained within mining structure columns in the '{0}' mining model. ...
  34. The '{1}' granularity attribute of the intermediate dimension '{0}' that is used to resolve many-to-many relationships should ...
  35. The '{4}' partition was not found in the '{3}' measure group in the '{2}' cube in the '{1}' database on the '{0}' server. ...
  36. The .NET Framework common language runtime was shut down by user code, such as in a user-defined function or CLR type. SQL ...
  37. The @keep_partition_changes property cannot be set to "true." This is because the @publication_compatibility_level property ...
  38. The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server ...
  39. The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', ...
  40. The @property parameter value must be one of the following: 'sync_type', 'priority', 'description', 'subscriber_security_mode', ...
  41. The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication. ...
  42. The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize with backup", or "initialize ...
  43. The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists ...
  44. The ability to INSERT NULL values into TIMESTAMP columns will be removed in a future version of SQL Server. Avoid using this ...
  45. The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. ...
  46. The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in ...
  47. The ability to use '#' and '#' as the name of temporary tables and stored procedures will be removed in a future version ...
  48. The ability to use '@' and names that start with '@' as Transact-SQL identifiers will be removed in a future version of SQL ...
  49. The ability to use string literals as column aliases will be removed in a future version of SQL Server. Avoid using this ...
  50. The ability to use the DEFAULT keyword as a default value will be removed in a future version of SQL Server. Avoid using ...
  51. The above grid contains the partitioning columns for the selected table. Select the column you want to use as the partitioning ...
  52. The AcceptPause property indicates whether the service can be paused. Values: TRUE or FALSE. A value of TRUE indicates the ...
  53. The AcceptStop property indicates whether the service can be stopped. Values: TRUE or FALSE. A value of TRUE indicates the ...
  54. The account running SQL Server Setup does not have administator rights on the computer. To continue, use an account with ...
  55. The account used to connect to server instance '{0}' does not have sufficient permissions to configure this instance as a ...
  56. The account used to connect to server instance '{0}' does not have sufficient permissions to configure this instance as a ...
  57. The AccountType attribute was not found. Ensure that the AttributeHierarchyEnabled property is set to True, and then process ...
  58. The AcquireConnection method call to the connection manager %1!s! failed with error code 2!8.8X!. There may be error messages ...
  59. The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server ...
  60. The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server ...
  61. The action you attempted to perform on a remote SQL Server instance failed because the action requires a SQL Server component ...
  62. The activated task was aborted because the invoked stored procedure '%1!s!' did not issue COMMIT or ROLLBACK on one or more ...
  63. The activated task was aborted due to an error (Error: %1!s!, State %2!s!). Check ERRORLOG or the previous "Broker:Activation" ...
  64. The Active Directory operation on publication '%1!s!' could not be completed because Active Directory client package is not ...
  65. The Activity Monitor is unable to execute queries against server {0}. Activity Monitor for this instance will be placed into ...
  66. The adapter encountered an unrecognized data type of %1!d!. This could be caused by a damaged input file (source) or by an ...
  67. The adapter was asked to write a string that was %1!I64d! bytes long, but all data must be less than 4294967295 bytes in ...
  68. The add device request was denied. A physical device named "%1!s!" already exists. Only one backup device may refer to any ...
  69. The address default type cannot have more than 1 section. The encoded address '{0}' has '{1}' sections. To continue, specify ...
  70. The administrative link password required to connect to the Distributor has been changed. Enter the new password in the following ...
  71. The advanced editor cannot be used with this component. The advanced editor displays only components with a single input. ...
  72. The advanced editor provides access to the low-level properties of data flow components. Additionally, the advanced editor ...
  73. The affinity mask specified conflicts with the IO affinity mask specified. Use the override option to force this configuration. ...
  74. The agent command line specified in the definition file '%1' references the same definition file. This type of recursive ...
  75. The agent failed to connect to the distribution database because of the following error: '%1!s!'. Ensure that replication ...