SQL Server 2008

  1. A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'. ...
  2. A pie chart displays value data as percentages of a total. Consider using a pie chart after the data has been aggregated ...
  3. A placeholder function parameter or operand was found in an expression. This should be replaced with an actual parameter ...
  4. A placeholder implementation will be generated for the destination object '{0}' to facilitate deferred creation of the actual ...
  5. A plan fingerprint is the same for all queries of the same general shape. If an application does not parameterize its queries, ...
  6. A possible infinite recompile was detected for SQLHANDLE %1!s!, PlanHandle %2!s!, starting offset %3!s!, ending offset %4!s!. ...
  7. A precedence constraint already exists between the specified executables. More than one precedence constraint is not allowed. ...
  8. A precedence constraint defines the workflow between two executables. The precedence constraint can be based on a combination ...
  9. A previous CTP installation of SQL Server 2008 is detected. You cannot install this release until the existing instances ...
  10. A previous FILESTREAM configuration attempt was incomplete. FILESTREAM may be in an inconsistent state until re-configured. ...
  11. A previous installation for this product is in progress. You must undo the changes made by that installation to continue. ...
  12. A previous installation required a reboot of the machine for changes to take effect. To proceed, restart your computer and ...
  13. A previous release of Microsoft Visual Studio 2008 is installed on this computer. Upgrade Microsoft Visual Studio 2008 to ...
  14. A previous restore operation was interrupted and did not complete processing on file '%1!s!'. Either restore the backup set ...
  15. A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this ...
  16. A previous upgrade that failed was detected. To retry the upgrade, remove the upgraded feature that failed, and then run ...
  17. A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration ...
  18. A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic ...
  19. A problem occurred attempting to delete row {0}. Error Source: {1}. Error Message: {2} Correct the errors and attempt to ...
  20. A profile may be associated with multiple SMTP accounts. If an account fails while sending an e-mail, the profile uses the ...
  21. A push subscription to the publication '%1!s!' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. ...
  22. A query connection is unavailable or not supported for the requested query execution environment. This is usually due to ...
  23. A query executing on %1 '%2' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge ...
  24. A query fingerprint is the same for all queries of the same general form, even if the queries have different inline literal ...
  25. A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified ...
  26. A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the ...
  27. A rate measure group must be related to a currency dimension (the dimension type must be Currency). No such measure group ...
  28. A rate measure group must be related to a currency dimension. Either no currency dimension exists (dimension type must be ...
  29. A read of the file '%1!s!' at offset %2!s! succeeded after failing %3!s! time(s) with error: %4!s!. Additional messages in ...
  30. A read operation on a large object failed while sending data to the client. A common cause for this is if the application ...
  31. A recursive update operation cannot be performed on the '%{strAttrID/}' attribute because it is not part of a parent-child ...
  32. A reference dimension with Materialization = 'Regular' cannot have a server time dimension as its intermediate dimension. ...
  33. A reference to attribute set '%1' cannot be resolved. An xsl:attribute-set of this name must be declared at the top-level ...
  34. A reference to key '%1' cannot be resolved. An xsl:key instruction of this name must be declared at the top-level of the ...
  35. A reference to variable or parameter '%1' cannot be resolved. The variable or parameter may not be defined, or it may not ...
  36. A referenced relationship cannot be set to Materialize if the selected dimension or measure group is linked. Additionally, ...
  37. A report parameter expression for the {0} {1}' uses the function RowNumber. RowNumber cannot be used in report parameter ...
  38. A request to start a full-text index population on table or indexed view '%1!s!' is ignored because a population is currently ...
  39. A request was made to open a module with a supported language but the module has a language transformation that is not valid. ...
  40. A required child element is missing under %1[%{strName/}%]%[/%{strName/}%]/%{strQName/} at line %d{iLine/}, column %d{iCol/} ...
  41. A required interface "%1" was not exposed by a Table-Valued Parameter Rowset. The Table-Valued Parameter could not be sent. ...
  42. A return value of data type varchar(max), nvarchar(max), varbinary(max), XML or other large object type can not be returned ...
  43. A row in the ModuleSubstitution table references a configuration item not defined in the ModuleConfiguration table. Module ...
  44. A rowcount validation request has been submitted to heterogeneous publisher %1!s! for article %2!s! of publication %3!s!. ...
  45. A scalar function that allows the caller of a stored procedure to determine whether or not the procedure has returned a cursor ...
  46. A schema contains database objects, such as tables, views, and stored procedures. A schema owner can be a database user, ...
  47. A security (SSPI) error occurred when connecting to another service broker: '%1!s!'. Check the Windows Event Log for more ...
  48. A semicolon (;) must be use to separate options in a notification options identifier. String '%1!s!' was found following ...
  49. A sequence node column was not found in the %{modelname/}, model. The Microsoft Sequence Clustering algorithm requires a ...
  50. A serious error occurred in the Service Broker message transmitter (operation %1!s!): Error: %2!s!, State: %3!s!. Message ...
  51. A server subscription can republish the data to, and be a synchronization partner with, other Subscribers. It has its own ...
  52. A session transaction cannot be nested inside an existing transaction. Session objects cannot be created inside a non-session ...
  53. A session transaction is already in progress, but a non-session write operation was initiated. After creating a session object, ...
  54. A set of customer data that can be used with the Query Data task on the Data Mining ribbon after models have been created. ...
  55. A set of sample rows will be extracted into a new spreadsheet. The sample will have at most {0} rows and will ensure {1}% ...
  56. A set of sample rows will be extracted into the "{0}" spreadsheet. The sample will have at most {1} rows and will ensure ...
  57. A setting '{0}' is found being implemented by both property '{1}' of object '{2}' and property '{3}' of object '{4}'. This ...
  58. A SharePoint Web application has content databases on a remote computer and the report server is running under an account ...
  59. A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: ...
  60. A single session may have different Execution Context IDs if it is running a parallel query (see "sys.dm_os_tasks.exec_context_id") ...
  61. A single session may have different Request IDs if it uses Multiple Active Result Sets, or MARS (see "sys.dm_exec_requests.request_id") ...
  62. A SKU violation has been discovered; this normally indicates an attempt to use features from a lower SKU version of the product ...
  63. A sort expression for the {0} '{1}' includes a variable reference. Variable values cannot be used in data row sort expressions. ...
  64. A sort expression for the {0} '{1}' includes an aggregate function. Aggregate functions cannot be used in data row sort expressions. ...
  65. A sort expression for the {0} {1}' uses aggregate function First, Last or Previous. These aggregate functions cannot be used ...
  66. A sort expression for the {0} {1}' uses the aggregate function RunningValue. RunningValue cannot be used in sort expressions. ...
  67. A SortMode value of Automatic is incompatible with the DataGridViewAutoFilterColumnHeaderCell type. Use the AutomaticSortingEnabled ...
  68. A source binding is missing for the OLAP mining structure, '%{structure/}' (column='%{column/}', nested column='%{nestedcolumn/}'). ...
  69. A SQL Server patch with a higher version has already been installed on SQL Server instance {4}, so the current SQL Server ...
  70. A stoplist cache cannot be generated while processing a full-text query or performing full-text indexing. There is not enough ...
  71. A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema ...
  72. A string literal contains an illegal hexadecimal escape sequence. The escape sequence is not supported in string literals ...
  73. A string value within the notification options identifier is too long. String with prefix '%1!s!' must be %2!s! characters ...
  74. A subscription database needs to be initialized with a snapshot of the publication data and schema unless it has already ...
  75. A summary page is not available for the {0} instance because the instance uses a previous version of Notification Services. ...