SQL Server 2012

  1. Assign values to the available variables in the cube. A corresponding report parameter will be created for each variable ...
  2. Assigning invalid value or object to variable "%1!s!". This error happens when a value is not appropriate for variables. ...
  3. Asynchronous-commit availability mode does not support automatic failover. For automatic failover, use synchronous-commit ...
  4. At input "%1!s!" (%2!d!), the virtual input column collection does not contain a virtual input column with lineage ID %3!d!. ...
  5. At least one action (Copy, Delete, Dump, Encrypt, Exists, Move, Sign, FCreate, FDelete, FRename, FExists, FDirectory) must ...
  6. At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an ...
  7. At least one column in the Available Input Columns table must be mapped to one column in the Available Lookup Columns table. ...
  8. At least one dataset in this report depends on data source '{0}'. If you delete the data source, you must bind each dependent ...
  9. At least one feature (SQL, AS, FullText) must be specified for SQL Server failover clustering. To continue, specify a feature ...
  10. At least one index column should be specified for the Cache connection manager. To specify an index column, set the Index ...
  11. At least one of the following settings must be enabled: Silence Interval, Silence Override Interval, or Force Rebuild Interval. ...
  12. At least one Oracle publisher meta data table does not exist in the Oracle publisher admin schema or the publisher schema ...
  13. At least one table or view must be selected before you can select the related tables. Use the check boxes next to each table ...
  14. At most, 300 columns can be added or updated per change to the table schema. Use the Transact-SQL Editor if you need to add ...
  15. At most, 300 parameters can be added or updated per change to the stored procedure. Use the Transact-SQL Editor if you need ...
  16. At the time of call to BCPColumns, the number of columns must be 0. BCPColumns can be called only once during a BCP operation ...
  17. Attaching the resource database in the same directory as sqlservr.exe at '%1!s!' failed as the database files do not exist. ...
  18. Attempt to access non-existent or uninitialized availability group with ID '%1!s!'. This is usually an internal condition, ...
  19. Attempt to find the input column named "%1!s!" failed with error code 2!8.8X!. The input column specified was not found in ...
  20. Attempt to find the input column with lineage ID %1!d! failed with error code 2!8.8X!. The input column was not found in ...
  21. Attempt to generate a string representation of the expression failed with error code 1!8.8X!. Failed when attempting to generate ...
  22. Attempt to parse the expression "%1!s!" failed and returned error code 2!8.8X!. The expression cannot be parsed. It might ...
  23. Attempt to parse the expression "%1!s!" failed. The expression might contain an invalid token, an incomplete token, or an ...
  24. Attempt to parse the expression "%1!s!" failed. The token "%2!s!" at line number "%3!s!", character number "%4!s!" was not ...
  25. Attempt to parse the expression failed. The expression contains an invalid or incomplete token. It may contain invalid elements, ...
  26. Attempt to perform an AlwaysOn Availability Groups operation on a system database, '%1!s!', failed. System databases are ...
  27. Attempt to set the data type properties on "%1!s!" failed with error code 2!8.8X!. The error occurred while attempting to ...
  28. Attempt to translate the query failed because the entity referenced in the query is not associated with any relationship. ...
  29. Attempted overwrite of read-only property. A property value set during report item definition generation cannot be reset ...
  30. Attempted to make an inconsistent change to a schema. Possible causes: deleting a schema that is in use by a Domain-Provider ...
  31. Attempted to set property mapping to target unsupported object type. This error occurs when passing an unsupported object ...
  32. Attempting an upgrade of SSIS from version "%1!s!" to version "%2!s!". The package is attempting to upgrade the runtime. ...
  33. Attempting to create an output with the name "%1!s!" for the XML table with the path "%2!s!" failed because the name is invalid. ...
  34. Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No ...
  35. Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). ...
  36. Attempting to set the result column for the expression "%1!s!" on %2!s! failed with error code 3!8.8X!. The input or output ...
  37. Attempting to upgrade a Management Data Warehouse of newer version '%1!s!' with an older version '%2!s!'. Upgrade aborted. ...
  38. Attribute '%{IMBIColumnId/}' of dimension '%{IMBITableId/}' has a RowNumberBinding, but the type of the attribute is not ...
  39. Attribute names in your entity contain reserved words. To run matching on this entity, either rename or delete the attributes. ...
  40. Attribute relationships do not exist between one or more levels in this hierarchy. The following levels do not have a direct ...
  41. Attribute relationships do not exist between one or more levels of this hierarchy. This may result in decreased query performance. ...
  42. Attribute {0} is an identifying attribute of these entities. These entities may become invalid if this attribute is not included. ...
  43. Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%1!s!' of type TEXT/NTEXT ...
  44. Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%1' of type TEXT/NTEXT or ...
  45. AttributePermission object is not supported for Business Intelligence Semantic Model databases running on an Analysis Services ...
  46. Attributes 'CompareOptions' and 'StringComparison' cannot be specified at the same time for a culture-sensitive operation ...
  47. Attributes of Binary type cannot be used in user defined hierarchies. The attribute '%{IMBIColumnId/}' in the dimension '%{IMBITableId/}' ...
  48. Audit '%1!s!' failed to %2!s!. For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers ...
  49. Audit '%1!s!' has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server ...
  50. Auto close is enabled. Only databases with auto close disabled can be added to an availability group. To turn off auto close, ...
  51. Auto detect sensitivity for minimum support. Setting this value to 1.0 causes the algorithm to autodetect the smallest appropriate ...
  52. Autogrow of file '%1!s!' in database '%2!s!' took %3!s! milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH ...
  53. Autogrow of file '%1!s!' in database '%2!s!' was cancelled by user or timed out after %3!s! milliseconds. Use ALTER DATABASE ...
  54. Automated backups for this availability group should occur on a secondary replica. If there is no secondary replica available, ...
  55. Automatic checkpointing is disabled in database '%1!s!' because the log is out of space. Automatic checkpointing will be ...
  56. Automatic feature selection has been applied to model, %{modelname/} due to the large number of attributes. Set MAXIMUM_INPUT_ATTRIBUTES ...
  57. Automatically cleanup the change tracking information by using the specified retention period. If off, change tracking information ...
  58. Automatically send feature usage reports for all instances of SQL Server Migration Assistant to Microsoft or your corporate ...
  59. Availability database '%1!s!', which is in the secondary role, is being restarted to resynchronize with the current primary ...
  60. Availability group '%1!s!' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is being ...
  61. Availability group '%1!s!' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is still ...
  62. Availability group '%1!s!' cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is ...
  63. Availability group '%1!s!' failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%2!s!) ...
  64. Availability group '%1!s!' failed to process %2!s!-%3!s! command. The local availability replica is not in a state that could ...
  65. Availability group '%1!s!' failed to process %2!s!-%3!s! command. The operation encountered SQL Server error %4!s! before ...
  66. Availability group '%1!s!' failed to process the %2!s!-%3!s! command. The availability group configuration has been updated. ...
  67. Availability group '%1!s!' failed to process the WSFC lease-renewal command. The local availability replica lease is no longer ...
  68. Availability group name to ID map entry for availability group '%1!s!' cannot be found in the Windows Server Failover Clustering ...
  69. Availability replica '%1!s!' cannot be added to availability group '%2!s!'. The availability group already contains an availability ...
  70. Availability replica '%1!s!' cannot be removed from availability group '%2!s!', because this replica is on the local instance ...
  71. Availability replica '%1!s!' cannot be removed from availability group '%2!s!'. The availability group does not contain an ...
  72. Availability replica '%1!s!' of availability group '%2!s!' cannot be brought online on this SQL Server instance. Another ...
  73. Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, ...
  74. Average duration of all completed executions of this query (see "sys.dm_exec_query_stats.total_elapsed_time" and "sys.dm ...
  75. Avoid creating linked dimensions to a source that contains UnaryOperatorColumns, CustomRollupColumns, or CustomRollupPropertiesColumns ...