SQL Server 2008

  1. The topology configuration has changed. The new configuration requires that you quiesce all nodes in the topology. For more ...
  2. The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology. ...
  3. The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all ...
  4. The topology view is not available when connected to '{0}'. To configure the topology, manually add the required nodes and ...
  5. The TopPercent function returns the smallest number of rows in descending order such that the sum of the rank expression ...
  6. The TopSum function returns the smallest number of rows in descending order such that the sum of the rank expression values ...
  7. The total number of keybindings of the linked %{typename/}, with the ID of '%{id/}', Name of '%{name/}' on the remote server ...
  8. The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover ...
  9. The trace log cannot be found at the default directory location. Trace logs will be created at the following location: %1 ...
  10. The tracer token ID (%1!s!) could not be found for Publisher %2!s!, database %3!s!, publication %4!s!. Use the stored procedure ...
  11. The transaction cannot be assigned because the connection object associated with the transaction and the connection object ...
  12. The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may ...
  13. The transaction for posting merge snapshot commands to the Publisher database had been chosen as a deadlock victim, the operation ...
  14. The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same ...
  15. The transaction log contains a record (logop %1!s!) that is not valid. The log has been corrupted. Restore the database from ...
  16. The transaction log for database '%1!s!' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc ...
  17. The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction. ...
  18. The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at ...
  19. The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable ...
  20. The TransSubscription.BackupInformation property must be set with valid backup information when creating a subscription with ...
  21. The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are ...
  22. The TSQL debugger has not been installed properly on the Visual Studio machine (ssdebugps.dll may not be registered properly). ...
  23. The type '{0}' is not marked with serialization attribute 'DatastoreSerializationAttribute'. Serialization and de-serialization ...
  24. The type '{0}' is not marked with serialization attribute 'DatastoreSerializationAttribute'. The path of the root document ...
  25. The type must be '[indexed view ]logbased[ (manualview|manualfilter|manualboth)]', '[serializable ]proc exec', or '(view|indexed ...
  26. The type of the first argument to NULLIF cannot be the NULL constant because the type of the first argument has to be known. ...
  27. The type of the value being assigned to variable "%1!s!" differs from the current variable type. Variables may not change ...
  28. The Type property for the dimension attributes must be set to a time type. The list of available time calculations from which ...
  29. The unary operation "%1!s!" failed with error code 2!8.8X!. An internal error occurred, or there is an out-of-memory condition. ...
  30. The unary operator column of the %{property/} attribute is not valid because either the attribute is not a parent attribute ...
  31. The uncompressed size of the file '{0}' has exceeded the size limit of '{1}' bytes imposed by SQL Replication's compression ...
  32. The unique constraint '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
  33. The unique index '%1!s!' on source table '%2!s!' is used by Change Data Capture. To alter or drop the index, you must first ...
  34. The unique index '%1!s!' on table '%2!s!' is used by Change Data Capture. The constraint using this index cannot be dropped ...
  35. The unique index '%1!s!' on table '%2!s!.%3!s!' is disabled and cannot be used as a unique index by Change Data Capture. ...
  36. The up to date mining model content cannot be displayed due to failures in project deployment. See the Output window for ...
  37. The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring ...
  38. The update operation failed because the data source view identifies the column (table '%{table/}', column '%{column/}') as ...
  39. The Update Statistics task ensures the query optimizer has up-to-date information about the distribution of data values in ...
  40. The Upgrade Advisor Analysis Wizard examines your instances of SQL Server 2000 and SQL Server 2005 for issues that can prevent ...
  41. The Upgrade Advisor detected a script that contains a colon (:) following a reserved keyword. In earlier versions of SQL ...
  42. The Upgrade Advisor detected duplicate login security identifiers (SID). Remove one of the logins and associated users before ...
  43. The Upgrade Advisor detected nonstandard column-level permissions on system objects. These permission changes will not be ...
  44. The Upgrade Advisor detected one or more user-defined login names that match the names of fixed server roles. Fixed server ...
  45. The Upgrade Advisor detected user-defined functions that are owned by the undocumented user system_function_schema. In SQL ...
  46. The Upgrade Advisor has detected client server connectivity protocols that are not supported in SQL Server 2008. Client applications ...
  47. The Upgrade Advisor Report Viewer displays the results of the analysis. Use this report to view a list of issues found during ...
  48. The upgrade process detected custom report items on the report server. You can continue with the upgrade, but you must then ...
  49. The URL %1!s! is not valid. This can happen when a scheme other than http or https is specified, or the URL is in an incorrect ...
  50. The URL specified by endpoint '%1!s!' is already registered to receive requests or is reserved for use by another service. ...
  51. The URL specified is not valid. This can happen when the server or proxy URL is null, or in an incorrect format. A valid ...
  52. The usage for the '%{column/}' column of the '%{model/}' mining model must be set to Key, because its source mining structure ...
  53. The Usage Type specified for the input columns to this transform cannot be read/write. Change the Usage Type to be read-only. ...
  54. The USE database statement failed because the database collation %1!s! is not recognized by older client drivers. Try upgrading ...
  55. The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in ...
  56. The use of the file connection manager has changed from specifying file names to specifying folder names. Do you want to ...
  57. The use of this file connection manager has changed from specifying folder names to specifying file names. Do you want to ...
  58. The user does not have permission to alter the current default stoplist '%1!s!'. To change the default stoplist of the database, ...
  59. The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%1!s! ...
  60. The user name of 'sys' is a reserved name in a SQL Server 2008 database. Before upgrade, you must rename all user names of ...
  61. The user running this Setup operation must have sufficient privileges to access registry and service control manager on remote ...
  62. The user transaction that has been started in user defined routine, trigger or aggregate "%1!s!" is not ended upon exiting ...
  63. The user-defined function (UDF) at line %d{Line/}, column %d{Column/} cannot be used as a data source for the current statement. ...
  64. The user-defined statistic '{0}' will not be scripted for article '{1}' because it references the unpublished column '{2}'. ...
  65. The username, '{0}', cannot be used in the domain controller. Please provide a valid username for the Analysis Services service. ...
  66. The users and groups member of this role will have privileges in all the Analysis Services objects associated with this role. ...
  67. The UsesDispositions property cannot be changed from its initial value. This occurs when the XML is edited and the UsesDispositions ...
  68. The valid new types of a log based indexed view article are 'indexed view logbased', 'indexed view logbased manualfilter', ...
  69. The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased ...
  70. The Validate method on the task failed, and returned error code 1!8.8X! (%2!s!). The Validate method must succeed and indicate ...
  71. The validation token for this partitioned snapshot may be corrupt. You must generate a new partitioned snapshot before initializing ...
  72. The value %1!d! specified for the code page parameter of the NULL function with data type "%2!s!" is not valid. The code ...
  73. The value %1!d! specified for the length parameter of the "NULL" function with data type %2!s! is negative and not valid. ...
  74. The value %1!d! specified for the length parameter of the cast to data type %2!s! is negative and not valid. The length must ...
  75. The value %1!d! specified for the precision parameter of the cast to data type "%2!s!" is not valid. Precision must be in ...