SQL Server 2008

  1. The schema change failed during execution of an internal replication procedure. For corrective action, see the other error ...
  2. The schema definition of the destination table '%1'.'%2' in the subscription database does not match the schema definition ...
  3. The schema for the article %1!s! was either not generated properly or was not applied properly during initial synchronization. ...
  4. The schema of the custom DataSet object implemented in the business logic handler does not match the schema of the source ...
  5. The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. ...
  6. The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, ...
  7. The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, ...
  8. The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this ...
  9. The schema {0} does not have any corresponding user or role. Schema objects are not supported in the target database version, ...
  10. The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same ...
  11. The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script ...
  12. The script exceeds the Transact-SQL IntelliSense maximum script size setting. You can change the setting on the Text Editor/Transact-SQL/IntelliSense ...
  13. 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. ...
  14. The Script Task "{0}" uses a version of Visual Studio Tools for Application (VSTA) that is not supported in this release ...
  15. The second argument in a Top or Bottom function must be a column. The error occurred at line %d{Line/}, column %d{Column/}. ...
  16. The security certificate bound to database principal (Id: %1!s!) has been disabled for use with BEGIN DIALOG. See the Books ...
  17. The security certificate bound to database principal (Id: %1!s!) has expired. Create or install a new certificate for the ...
  18. The security certificate bound to database principal (Id: %1!s!) is not yet valid. Either wait for the certificate to become ...
  19. The security mode specified requires the server '%1!s!' to be registered as a linked server. Use sp_addlinkedserver to add ...
  20. The security settings that are defined for this item will be replaced by the security settings of its parent {0}. Do you ...
  21. The SELECT item identified by the ORDER BY number %1!s! contains a variable as part of the expression identifying a column ...
  22. The SELECT item identified by the ORDER BY number {0} contains a variable as part of the expression identifying a column ...
  23. The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match ...
  24. The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match ...
  25. The selected action cannot be completed because of the following error. {0} This error may have occurred because the definition ...
  26. The selected configuration could not be moved after the next configuration. Verify that a configuration is selected and there ...
  27. The selected configuration could not be moved before the previous configuration. Verify that a configuration is selected ...
  28. The selected connection manager does not use a SQL Server provider. Bulk insert operations require a connection that uses ...
  29. The selected connection manager uses an earlier version of a SQL Server provider. Bulk insert operations require a connection ...
  30. The selected data extension {0} cannot be loaded. Verify that the selected data extension is correctly registered in RSReportDesigner.config, ...
  31. The selected database contains foreign keys that create a cycle. Publishing data only is not supported for databases with ...
  32. The selected database does not have the Recovery Model property set to full. This is required in order to back up the transaction ...
  33. The selected instance for installation is already installed and clustered on computer {0}. To continue, select a different ...
  34. The selected instance is already installed and clustered on this or other cluster nodes. To continue, use AddNode to add ...
  35. The selected instance is clustered and cannot be removed as specified. To remove the selected instance, select "Remove Node" ...
  36. The selected instance is SQL Server 2000 at Service Pack 4 (SP4) and meets the requirements or is not a SQL Server 2000 instance. ...
  37. The selected members cannot be moved together because they are not from the same level in the hierarchy. Only members that ...
  38. The selected Reporting Services instances will be removed from the scale out deployment. To add a Reporting Services instance ...
  39. The selected SQL Server 2000 instance does not meet the requirements for upgrade. To continue install Microsoft SQL Server ...
  40. The selected SQL Server 2008 instance does not meet the requirements for build-to-build upgrade. To continue, you must remove ...
  41. The selected SQL Server 2008 instance meets the requirements for build-to-build upgrade or the selected instance is not SQL ...
  42. The SelectedItems property of the DrillthroughContext parameter refers to items in more than one context. SelectedItems must ...
  43. The SelectedPath property of the DrillthroughContext parameter is "{0}", which is not equal to or a subset of the longest ...
  44. The semantic query engine has not been initialized. The Initialize method must be called to set the model and data extension ...
  45. The sensitive data in the package '{0}' is encrypted with a password. Please provide the password. Without the password, ...
  46. The sensitive data in the package is encrypted with a password. Please provide the password. Without the password, the package ...
  47. The server '%1!s!' is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall ...
  48. The server '{0}' can not be configured as a peer. Peer-To-Peer replication only supports server instances running Microsoft ...
  49. The server '{0}' was successfully defected. You should remove the MSX account manually if it is not required by other TSX ...
  50. The server configuration information has been updated. SqlRemoteBlobContext object is not valid. Recreate the SqlRemoteBlobContext ...
  51. The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %1!s!. ...
  52. The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with ...
  53. The server instance %1!s! rejected configure request; read its error log file for more information. The reason %2!s!, and ...
  54. The server name is not found in the connection string '{0}'. Verify that the server name is included in the connection string, ...
  55. The server network address "%1!s!" can not be reached or does not exist. Check the network address name and that the ports ...
  56. The server option 'collation name' in linked server '%1!s!' for OLE DB provider '%2!s!' has collation id %3!s! which is not ...
  57. The server property, AllowedBrowsingFolders, determines which folders appear in this dialog box. To add or remove folders ...
  58. The server resumed execution after being idle %1!s! seconds. This is an informational message only. No user action is required. ...
  59. The server was stopped because SQL Server Audit '%1!s!' is configured to shut down on failure. To troubleshoot this issue, ...
  60. The server was unable to complete its initialization sequence because the available network libraries do not support the ...
  61. The server was unable to initialize encryption because of a problem with a security library. The security library may be ...
  62. The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt ...
  63. The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user ...
  64. The ServerHTTPRequest property can not be used when loading a document asynchronously and is only supported on Windows NT ...
  65. The service account could not be retrieved. Use the ASSVCACCOUNT service account command line parameter to specify the service ...
  66. The service account is not in the domain group. Ensure that the service account is a member of the domain group for the SQL ...
  67. The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, ...
  68. The Service Broker in database "%1!s!" cannot be enabled because there is already an enabled Service Broker with the same ...
  69. The Service Broker in database "%1!s!" will be disabled because the Service Broker GUID in the database (%2!s!) does not ...
  70. The service did not respond to the start or control request in a timely fashion, you need administrator privileges to be ...
  71. The service failed to start for an unknown reason. For more information, see the event logs and the SQL Server error logs. ...
  72. The service must be running to allow reencryption of the service master key. Encrypted secrets may not be recoverable if ...
  73. The service pack level of SQL Server instance {2} is not equal to the service pack level expected by the SQL Server patch. ...
  74. The Service Start Mode parameter cannot be disabled on the active node. Change the service state to either manual or automatic ...
  75. The service that you are trying to manage is not supported by the WMI provider. Note that you can only manage SQL Server ...