SQL Server 2016

  1. A NumaNode with the id if {0} does not exist on this system. Use SetAffinityToRange(startNumaNodeId, endNumaNodeId, affinityMask, ...
  2. A number from 1-5 indicating the current memory state of the server. 1:No pressure, 2:Low Pressure,3:Medium Pressure,4:High ...
  3. A number from 1-5 indicating the current memory state of the server. 1:No pressure, 2:Low Pressure,3:Medium Pressure,4:High ...
  4. A number that determines the return value: for Sunday=1 through Saturday=7, use 1; for Monday=1 through Sunday=7, use 2; ...
  5. A page that should have been constant has changed (expected checksum: %1!s!, actual checksum: %2!s!, database %3!s!, file ...
  6. A PageBreak property was detected in the data region, rectangle, or group {0}' SQL Server 2008 Reporting Services does not ...
  7. A PageBreak property was removed from the data region, rectangle, or group {0}'. SQL Server 2008 Reporting Services does ...
  8. A parameter named '{0}' already exists in the parameter collection. Parameter names must be unique in the parameter collection. ...
  9. A parameter with type return value is not the first parameter, or there are more than one parameter of type return value. ...
  10. A parent binding (schema '%{parschema/}', table '%{partable/}') and a child binding (schema '%{childschema/}' table '%{childtable/}') ...
  11. A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL ...
  12. A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'. ...
  13. A PerspectiveColumn in perspective '%{persp/}' refers to column '%{perspcolumn/}' in table '%{persptable/}', but it belongs ...
  14. A PerspectiveColumn in table '%{persptable/}' in perspective '%{persp/}' refers to a column '%{column/}' that has been deleted. ...
  15. A PerspectiveColumn in table '%{persptable/}' in perspective '%{persp/}' refers to an invalid column with ID '%{colID/}'. ...
  16. A PerspectiveHierarchy in perspective '%{persp/}' refers to hierarchy '%{persphierarchy/}' in table '%{persptable/}', but ...
  17. A PerspectiveHierarchy in table '%{persptable/}' in perspective '%{persp/}' refers to a hierarchy '%{hier/}' that has been ...
  18. A PerspectiveHierarchy in table '%{persptable/}' in perspective '%{persp/}' refers to an invalid hierarchy with ID '%{colID/}'. ...
  19. A PerspectiveMeasure in perspective '%{persp/}' refers to measure '%{perspmeasure/}' in table '%{persptable/}', but it belongs ...
  20. A PerspectiveMeasure in table '%{persptable/}' in perspective '%{persp/}' refers to a measure '%{measure/}' that has been ...
  21. A PerspectiveMeasure in table '%{persptable/}' in perspective '%{persp/}' refers to an invalid measure with ID '%{colID/}'. ...
  22. A pie chart displays value data as percentages of a total. Consider using a pie chart after the data has been aggregated ...
  23. A placeholder function parameter or operand was found in an expression. This should be replaced with an actual parameter ...
  24. A placeholder implementation will be generated for the destination object '{0}' to facilitate deferred creation of the actual ...
  25. A plan fingerprint is the same for all queries of the same general shape. If an application does not parameterize its queries, ...
  26. A positive integer that sets the periodicity value in the given table. Set 0 for no periodicity, 1 for auto-detection of ...
  27. A possible infinite recompile was detected for SQLHANDLE %1!s!, PlanHandle %2!s!, starting offset %3!s!, ending offset %4!s!. ...
  28. A possible infinite recompile was detected for the natively compiled module with ID '%1!s!' in database with ID '%2!s!'. ...
  29. A PowerPivot workbook that is published to SharePoint cannot be modified. Click OK to save a copy to your computer and continue ...
  30. A precedence constraint already exists between the specified executables. More than one precedence constraint is not allowed. ...
  31. A precedence constraint defines the workflow between two executables. The precedence constraint can be based on a combination ...
  32. A previous column master key rotation is already in progress, so some keys already have two encrypted values with different ...
  33. A previous FILESTREAM configuration attempt was incomplete. FILESTREAM may be in an inconsistent state until re-configured. ...
  34. A previous installation for this product is in progress. You must undo the changes made by that installation to continue. ...
  35. A previous installation required a reboot of the machine for changes to take effect. To proceed, restart your computer and ...
  36. A previous restore operation was interrupted and did not complete processing on file '%1!s!'. Either restore the backup set ...
  37. A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this ...
  38. A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group ...
  39. A previous upgrade that failed was detected. To retry the upgrade, remove the upgraded feature that failed, and then run ...
  40. A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration ...
  41. A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic ...
  42. A problem occurred attempting to delete row {0}. Error Source: {1}. Error Message: {2} Correct the errors and attempt to ...
  43. A profile may be associated with multiple SMTP accounts. If an account fails while sending an e-mail, the profile uses the ...
  44. A project deployment file (.ispac extension) is required in order to execute containers or packages. Build the project and ...
  45. A project for creating a new Business Intelligence Semantic Model for an Analysis Services database running in Vertipaq Real ...
  46. A property named '{1}' was found in the project file '{0}'. This property normally should not be specified in the project ...
  47. A publishing loop has been detected by the PublishingQueue, which has LoopThreshold={0}, while publishing to the subscribed ...
  48. A publishing loop has been detected by the PublishingQueue, which has LoopThreshold={0}, while publishing to the subscribed ...
  49. A push subscription to the publication '%1!s!' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. ...
  50. A query connection is unavailable or not supported for the requested query execution environment. This is usually due to ...
  51. A query executing on %1 '%2' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge ...
  52. A query fingerprint is the same for all queries of the same general form, even if the queries have different inline literal ...
  53. A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified ...
  54. A query that accesses memory optimized tables using the READ COMMITTED isolation level, cannot access disk based tables when ...
  55. A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the ...
  56. A rate measure group must be related to a currency dimension (the dimension type must be Currency). No such measure group ...
  57. A rate measure group must be related to a currency dimension. Either no currency dimension exists (dimension type must be ...
  58. 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 ...
  59. A read operation on a large object failed while sending data to the client. A common cause for this is if the application ...
  60. A reboot from a previous installation is pending. It may cause DQS install failure. Would you like to continue? {0}/{1}] ...
  61. A record (%d{recordSize/} bytes) was encountered that exceeds the maximum page size of the storage object (%d{pageSize/} ...
  62. A recursive derived hierarchy level cannot be added. Members with the following codes participate in circular relationships: ...
  63. A recursive update operation cannot be performed on the '%{strAttrID/}' attribute because it is not part of a parent-child ...
  64. A reference dimension with Materialization = 'Regular' cannot have a server time dimension as its intermediate dimension. ...
  65. A reference to attribute set '%1' cannot be resolved. An xsl:attribute-set of this name must be declared at the top-level ...
  66. A reference to key '%1' cannot be resolved. An xsl:key instruction of this name must be declared at the top-level of the ...
  67. A reference to variable or parameter '%1' cannot be resolved. The variable or parameter may not be defined, or it may not ...
  68. A reference to {0} could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM ...
  69. A referenced relationship cannot be set to Materialize if the selected dimension or measure group is linked. Additionally, ...
  70. A referential integrity constraint violation occurred: A primary key property that is a part of referential integrity constraint ...
  71. A referential integrity constraint violation occurred: The property values that define the referential constraints are not ...
  72. A referential integrity constraints violation occurred: Not all of the property values that define referential integrity ...
  73. A relationship from the '{0}' AssociationSet is in the '{1}' state. Given multiplicity constraints, a corresponding '{2}' ...
  74. A relationship has more than one ProcessingState element, which is not allowed. This may indicate corrupt database metadata. ...
  75. A relationship multiplicity constraint violation occurred: An EntityReference can have no more than one related object, but ...