SQL Server 2016

  1. The retention period for change tracking information. Change information will be retained for at least the time period that ...
  2. The retention period for the distribution database must be greater than the retention period of any existing non-merge publications. ...
  3. The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to ...
  4. The return table column "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using ...
  5. The return type is determined by the type of the evaluated result of expression. If the expression result is integer, decimal, ...
  6. The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. ...
  7. The returned rows appear in the Results pane and the database server continues to retain the result set in its local memory, ...
  8. The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE FROM DATABASE_SNAPSHOT ...
  9. The ring index n ({0}) passed to STInteriorRingN is less than 1. The number must be greater than or equal to 1 and should ...
  10. The ROLAP database cannot create an index on the view for the '%{schema/}' schema, '%{table/}' table. Verify that the requirements ...
  11. The role 'DatabaseMailUserRole' does not exist in the current database. This role is required for database notifications. ...
  12. The role assignment on the root folder cannot be deleted. At least one role assignment must be defined for the root folder ...
  13. The Role for the End with the EntitySet {0} in the AssociationSet {1} was not supplied and the End found matches one that ...
  14. The role for the replica '{0}' has already changed before failover. Verify the replica role, and re-run the Failover Wizard ...
  15. The Role, '%{role/}', for the RelationshipEnd is not valid because this name is a reserved word, contains one or more invalid ...
  16. The roll forward start point is now at log sequence number (LSN) %1!s!. Additional roll forward past LSN %2!s! is required ...
  17. The root component associated with '{0}' ('{1}') does not match the original root component ('{2}'). Check to make sure that ...
  18. The root node name of the query trace retrieval operation has the value '%{nodename/}', which does not correspond to any ...
  19. The root of the specified directory, "{1}", for the {0} parameter does not exist or is not found. Specify a valid path for ...
  20. The row filter for the table, '%{table/}', of the mining model , '%{model/}' , is invalid. The specified filter expression ...
  21. The row size limit of %1!s! bytes for memory optimized system versioned tables has been exceeded. Please simplify the table ...
  22. The row was not found at the Subscriber when applying the replicated %1!s! command for Table '%2!s!' with Primary Key(s): ...
  23. The rowset does not contain any column with offset %1!s!. Back up the publication database and contact Customer Support Services. ...
  24. The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last ...
  25. The rule '{0}' has no ExpressionXml defined, and the ExpressionGeneratorType is not defined. The ExpressionGeneratorType ...
  26. The rule '{0}' has no ExpressionXml defined, but the element is optional only for Comparison type rules. For all other rules ...
  27. The rule '{0}' is defined as a cluster comparison, but the ExpressionXml element was specified. This element is not allowed ...
  28. The rule cannot determine whether Windows Firewall is enabled. Any access from a remote computer will be blocked if a firewall ...
  29. The rule cannot verify Internet access on this version of Windows. There might be delays in starting a .NET application like ...
  30. The runtime connection manager with the ID "%1!s!" cannot be found. Verify that the connection manager collection has a connection ...
  31. The runtime object cannot be loaded from the specified XML node. This happens when trying to load a package or other object ...
  32. The same column(s) of the same row was updated at both '%1' and '%2'. The resolver chose the update from '%3' as the winner. ...
  33. The SaveToSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
  34. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the axis has more than one ...
  35. The scalar values property for the {2} of the {0} {1}' is set to true. Scalar cannot be true if the dynamic grouping has ...
  36. The scalar values property for the {2} of the {0} {1}' is set to true. Therefore the specified label expression will be ignored. ...
  37. The scale %1!u! exceeded the maximum limit of 7 for time/datetime2/datetimeoffset column %2!Iu!. InMemory Rowset creation ...
  38. The schedule '{0}' already exists and cannot be created or renamed. This error occurs when the schedule name is not unique. ...
  39. The schedule '{0}' at the Share Point site '{1}' already exists and cannot be created or renamed. This error occurs when ...
  40. The schedule '{0}' cannot be found. The schedule identifier that is provided to an operation cannot be located in the catalog. ...
  41. The schedule has been altered outside of PowerPivot. Use the Manage Data Refresh page to update and re-save the schedule. ...
  42. The schedule has been altered outside of PowerPivot. Use the Manage Data Refresh page to update and re-save the schedule." ...
  43. The schedule or workbook was updated while you were editting the schedule. Please reload the schedule and reapply any changes. ...
  44. The schedule was not attached to the specified job. The caller must own the job or the operation must be performed by a sysadmin. ...
  45. The schema at the Publisher (version: %2!d! and guid: '%1') does not match the schema at the Subscriber (version: %4!d! and ...
  46. The schema change failed during execution of an internal replication procedure. For corrective action, see the other error ...
  47. The schema definition of the destination table '%1'.'%2' in the subscription database does not match the schema definition ...
  48. The schema for the article %1!s! was either not generated properly or was not applied properly during initial synchronization. ...
  49. The schema of the custom DataSet object implemented in the business logic handler does not match the schema of the source ...
  50. The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. ...
  51. The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, ...
  52. The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, ...
  53. The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this ...
  54. The schema {0} does not have any corresponding user or role. Schema objects are not supported in the target database version, ...
  55. The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same ...
  56. The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script ...
  57. The script contains syntax that is not supported by the version of SQL Server that is associated with the database project. ...
  58. The script exceeds the Transact-SQL IntelliSense maximum script size setting. You can change the setting on the Text Editor/Transact-SQL/IntelliSense ...
  59. The script level for '%1!s!' in database '%2!s!' cannot be downgraded from %3!s! to %4!s!, which is supported by this server. ...
  60. The Script Task "{0}" uses version {1}.{2} script that is not supported in this release of Integration Services. To run the ...
  61. The scripting options specified for TargetServerVersion and TargetDatabaseEngineType are not valid. Change the version of ...
  62. The search property '%1!s!' already exists in the search property list. Specify a search property name that is unique within ...
  63. The search property '%1!s!' does not exist, or you do not have permission to perform this action. Verify that the correct ...
  64. The search property list '%1!s!' already exists in the current database. Duplicate search property list names are not allowed. ...
  65. The search property list '%1!s!' does not exist or you do not have permission to perform this action. Verify that the correct ...
  66. The second argument in a Top or Bottom function must be a column. The error occurred at line %d{Line/}, column %d{Column/}. ...
  67. The second parameter passed to function %{funcName/} is invalid. Please specify 0 for the Step Unit or 1 for the Step Size. ...
  68. The second table expression will be evaluated for each row in the first table. Returns the crossjoin of the first table with ...
  69. The second table expression will be evaluated for each row in the first table. Returns the crossjoin of the first table with ...
  70. The secondary replica that you selected to become the new primary replica does not belong to the specified availability group. ...
  71. The secret specified for the database credential '%1!s!' is invalid. The secret must be a valid password for the remote stretch ...
  72. The section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, ...
  73. The security certificate bound to database principal (Id: %1!s!) has been disabled for use with BEGIN DIALOG. See the Books ...
  74. The security certificate bound to database principal (Id: %1!s!) has expired. Create or install a new certificate for the ...
  75. The security certificate bound to database principal (Id: %1!s!) is not yet valid. Either wait for the certificate to become ...