SQL Server 2012

  1. The -AsTemplate option is set. You must either specify an argument to the -Version parameter or set your location to a SQL ...
  2. The .NET Framework common language runtime was shut down by user code, such as in a user-defined function or CLR type. SQL ...
  3. The /IAcceptSQLServerLicenseTerms command line parameter is missing or has not been set to true. It is a required parameter ...
  4. The @keep_partition_changes property cannot be set to "true." This is because the @publication_compatibility_level property ...
  5. The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server ...
  6. The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', ...
  7. The @property parameter value must be one of the following: 'sync_type', 'priority', 'description', 'subscriber_security_mode', ...
  8. The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication. ...
  9. The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize with backup", or "initialize ...
  10. The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists ...
  11. The ability to INSERT NULL values into TIMESTAMP columns will be removed in a future version of SQL Server. Avoid using this ...
  12. The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. ...
  13. The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in ...
  14. The ability to use '#' and '#' as the name of temporary tables and stored procedures will be removed in a future version ...
  15. The ability to use '@' and names that start with '@' as Transact-SQL identifiers will be removed in a future version of SQL ...
  16. The ability to use string literals as column aliases will be removed in a future version of SQL Server. Avoid using this ...
  17. The ability to use the DEFAULT keyword as a default value will be removed in a future version of SQL Server. Avoid using ...
  18. The above Discover XMLA query returns available data sources for the Analysis server and information required to connect ...
  19. The above grid contains the partitioning columns for the selected table. Select the column you want to use as the partitioning ...
  20. The absolute value of the increment for sequence object '%1!s!' must be less than or equal to the difference between the ...
  21. The AcceptPause property indicates whether the service can be paused. Values: TRUE or FALSE. A value of TRUE indicates the ...
  22. The AcceptStop property indicates whether the service can be stopped. Values: TRUE or FALSE. A value of TRUE indicates the ...
  23. The account running SQL Server Setup does not have administator rights on the computer. To continue, use an account with ...
  24. The account that is running SQL Server Setup does not have one or all of the following rights: the right to back up files ...
  25. The account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing ...
  26. The account used to connect to server instance '{0}' does not have sufficient permissions to configure this instance as a ...
  27. The account used to connect to server instance '{0}' does not have sufficient permissions to configure this instance as a ...
  28. The AccountType attribute was not found. Ensure that the AttributeHierarchyEnabled property is set to True, and then process ...
  29. The action type '{0}' is not valid for the DatastoreProperties element. The only valid action type is StoreDatastorePropertiesAction. ...
  30. The action type '{1}' is not valid for the {0} element. The only valid actions are ExpandUserVisibleFeatureAction, SetFeatureScenarioAction, ...
  31. The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server ...
  32. The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server ...
  33. The action you attempted to perform on a remote SQL Server instance failed because the action requires a SQL Server component ...
  34. The activated task was aborted because the invoked stored procedure '%1!s!' did not issue COMMIT or ROLLBACK on one or more ...
  35. The activated task was aborted due to an error (Error: %1!s!, State %2!s!). Check ERRORLOG or the previous "Broker:Activation" ...
  36. The activation message. The message may contain the name of the activation stored procedure, messages that were passed back ...
  37. The Active Directory operation on publication '%1!s!' could not be completed because Active Directory client package is not ...
  38. The Activity Monitor is unable to execute queries against server {0}. Activity Monitor for this instance will be placed into ...
  39. The adapter encountered an unrecognized data type of %1!d!. This could be caused by a damaged input file (source) or by an ...
  40. The adapter was asked to write a string that was %1!I64d! bytes long, but all data must be less than 4294967295 bytes in ...
  41. The add device request was denied. A physical device named "%1!s!" already exists. Only one backup device may refer to any ...
  42. The address default type cannot have more than 1 section. The encoded address '{0}' has '{1}' sections. To continue, specify ...
  43. The administrative link password required to connect to the Distributor has been changed. Enter the new password in the following ...
  44. The Advanced Data Warehouse Destination enables you load data into Advanced Data Warehouse. In a package workflow, you can ...
  45. The advanced editor cannot be used with this component. The advanced editor displays only components with a single input. ...
  46. The advanced editor provides access to the low-level properties of data flow components. Additionally, the advanced editor ...
  47. The affinity specified conflicts with the IO affinity mask specified. Change the affinity setting to use different CPUs than ...
  48. The agent command line specified in the definition file '%1' references the same definition file. This type of recursive ...
  49. The agent failed to connect to the distribution database because of the following error: '%1!s!'. Ensure that replication ...
  50. The agent failed to obtain the distributor and publisher login information from the subscription database due to the following ...
  51. The agent failed to obtain the distributor's login information from the subscriber database due to the following error: '%1!s!' ...
  52. The agent failed to obtain the publisher login information from the distribution database due to the following error: '%1!s!' ...
  53. The agent failed to obtain the subscriber's linked server information from the distribution database due to the following ...
  54. The agent failed to obtain the subscriber's login information from the distribution database due to the following error: ...
  55. The agent profile creation process cannot validate the specified agent parameter value. '%1!s!' is not a valid value for ...
  56. The agent profile creation process cannot validate the specified agent parameter value. '%1!s!' is not a valid value for ...
  57. The agent profile creation process cannot validate the specified agent parameter value: the profile_id %1!s! does not exist ...
  58. The aggregate component encountered too many distinct key combinations. It cannot accommodate more than %1!u! distinct key ...
  59. The aggregate component encountered too many distinct values while calculating the count distinct aggregate. It cannot accommodate ...
  60. The Aggregate transformation has encountered %1!d! distinct values while performing a "count distinct" aggregation on "%2!s!". ...
  61. The Aggregate transformation has encountered %1!d! key combinations. It has to re-hash data because the number of key combinations ...
  62. The aggregation design operation cannot be executed since it is attempting to modify the contents of the read only database ...
  63. The aggregation design operation is currently running for the '%{aggdesign/}' aggregation design object. Usage-based optimization ...
  64. The aggregation design with an ID of '%{aggdesignid/}', of the '%{partition/}' partition, does not correspond to an existing ...
  65. The aggregation function of the %{operand/} left operand of the measure expression of the %{measure/} measure must be sum, ...
  66. The aggregation function of the %{operand/} right operand of the measure expression of the %{measure/} measure must be sum, ...
  67. The aggregation function of the '%{measure/}' measure must be sum, count, min, or max because the function has a measure ...
  68. The aggregation should not include both the '{0}' and '{1}' attributes, because there is a relationship from '{0}' to '{1}'. ...
  69. The AggregationUsage property should be set to 'Full' because either the attribute or the parent attribute (if the dimension ...
  70. The alert engine failed to register notification-callback with the eventlog process. Alert processing will now occur via ...
  71. The alert for 'oldest unsent transaction' has been raised. The current value of '%1!s!' surpasses the threshold '%2!s!'. ...
  72. The algorithm provider for the %{AlgoName/} data mining algorithm does not expose a mandatory interface for custom functions. ...
  73. The algorithm provider for the '%{AlgoName/}' data mining algorithm cannot be created; its ProgID is missing in the server ...
  74. The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the ...
  75. The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work ...