SQL Server 2008

  1. The OLE DB provider "%1!s!" for linked server "%2!s!" reported different metadata at run time for table "%3!s!", column "%4!s!". ...
  2. The OLE DB provider "%1!s!" for linked server "%2!s!" returned a "%3!s!" index "%4!s!" with the incorrect bookmark ordinal ...
  3. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The column "%3!s!" (compile-time ...
  4. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata for a column. The name was changed at ...
  5. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. An extra column was supplied during ...
  6. The OLE DB provider "%1!s!" for linked server "%2!s!" supplied inconsistent metadata. The object "%3!s!" was missing the ...
  7. The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide collation data ...
  8. The OLE DB provider "%1!s!" for linked server "%2!s!" supports column level collation, but failed to provide the metadata ...
  9. The OLE DB provider '%1!s!' for linked server '%2!s!' provided invalid collation. LCID = %3!s!, Compflags = %4!s!, SortOrder ...
  10. The OLE DB provider used by the OLE DB adapter does not support IConvertType. Set the adapter's ValidateColumnMetaData property ...
  11. The OLE DB Provider {0} is not installed or is not valid. Do you want to reset the connection string? If you click OK, the ...
  12. The ON clause at line %d{Line/}, column %d{Column/}, is not valid. Columns specified in the ON clause must be scalar, and ...
  13. The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online. ...
  14. The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. An offline restore ...
  15. The online restore to database '%1!s!' failed. It may be appropriate to perform an offline restore instead. To force an offline ...
  16. The only configurable property for a cached HOLAP object is Silence Interval, which must be specified as zero or greater. ...
  17. The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. ...
  18. The OPENROWSET and OPENDATASOURCE functions support ad hoc connections to remote data sources without linked or remote servers. ...
  19. The operating system returned error %1!s! to SQL Server during a %2!s! at offset %3!s! in file '%4!s!'. Additional messages ...
  20. The operating system returned error %1!s! while creating the file '%2!s!'. Verify that the path exists and that the SQL Server ...
  21. The operating system returned error 5 (ACCESS_DENIED) while creating an ETW tracing session. Ensure that the SQL Server startup ...
  22. The operating system version does not meet the minimum requirements for this product. For more information, see hardware ...
  23. The operation cannot be completed because the file extension is either missing or it is not valid. Valid file extensions ...
  24. The operation cannot be completed because the memory quota estimate (%d{Request/}MB) exceeds the available system memory ...
  25. The operation cannot be executed since the database folder '%{dir_name/}' for the database with the name of '%{db_name/}', ...
  26. The operation cannot be executed since the database folder '%{dir_name/}' for the database with the name of '%{db_name/}', ...
  27. The operation could not be completed. The specified '%1!s!' value, %2!s!, causes the sum of minimums on all resource pools ...
  28. The operation could not be performed because OLE DB provider "%1!s!" for linked server "%2!s!" was unable to begin a distributed ...
  29. The operation failed because the Windows SharePoint Services object model is not installed on the report server. Install ...
  30. The operation is not valid because of the current state of the object. You can use the FetchAllProperties method to retrieve ...
  31. The option {0} is set to true for primary key defined on the table {1}. This option is not supported in the target database ...
  32. The options on this page only apply to when the frame style is set to "Circular", "Rectangular", "Rounded rectangular" or ...
  33. The options on this page only apply when the frame style is set to "Circular", "Rectangular", "Rounded rectangular" or "Auto ...
  34. The options you have selected are not secure. The user name and password will be sent as plain text to the specified Web ...
  35. The OPTMIZED_PREDICTION_COUNT parameter for the '%{modelname/}' model is not supported. OPTMIZED_PREDICTION_COUNT must be ...
  36. The Oracle INSTR(string, substring) function can be converted to a SQL Server CHARINDEX function call, or to a call to the ...
  37. The Oracle INSTR(string, substring, position) function can be converted to SQL Server CHARINDEX function call or call to ...
  38. The Oracle Publisher name is '%1!s!' and the Oracle Subscriber name is '%2!s!'. Bidirectional Oracle publishing requires ...
  39. The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ...
  40. The Oracle server %1!s! is already defined as the Publisher %2!s! on the Distributor %3!s!].[%4!s!]. Drop the Publisher or ...
  41. The Oracle SUBSTR(string, portion, substring_length) function can be converted to SQL Server SUBSTRING function call, or ...
  42. The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless ...
  43. The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command ...
  44. The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset '%1!s!'. The order ...
  45. The order of the data in the stream does not conform to the ORDER hint specified for the CLR TVF '%1!s!'. The order of the ...
  46. The output column "%1!s!" (%2!d!) on output "%3!s!" (%4!d!) and component "%5!s!" (%6!d!) is not subsequently used in the ...
  47. The output column with lineage ID "%1!d!" is incorrectly mapped to an input column. The CopyColumnId property of the output ...
  48. The output columns' metadata does not match the associated input columns' metadata. The output columns' metadata will be ...
  49. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has code page %2!d! and the ...
  50. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has maximum length %2!d! and ...
  51. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has precision %2!d! and the ...
  52. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has scale %2!d! and the input ...
  53. The output file cannot be appended. Column "%1!s!" matches by name, but the column in the file has type %2!s! and the input ...
  54. The output file was written by an incompatible version and cannot be appended. The file may be an older file format that ...
  55. The output name cannot be changed. There is the dangling output, which is not shown in the list of available outputs, with ...
  56. The output with ID %1!d! of Aggregate component is not used by any component. Please either remove it or associate it with ...
  57. The package "{0}" already exists on the server. Do you want to overwrite the package at destination? Click Yes to overwrite ...
  58. The package %1!s! can not be saved to the file system since its protection level is server storage. Use the encrypt action ...
  59. The package cannot be loaded because the state of the digital signature violates signature policy. Error 1!8.8X! "%2!s!" ...
  60. The package cannot be loaded. This occurs when attempting to load an older version package, or the package file refers to ...
  61. The Package Configuration Wizard helps you create configurations which can be used to dynamically configure the package during ...
  62. The package contains one or more event handlers for this task. Deleting the task will also delete the event handlers and ...
  63. The package failed during execution because the checkpoint file cannot be loaded. Further execution of the package requires ...
  64. The package has been migrated to a later version during loading. It must be reloaded to complete the process. This is an ...
  65. The package is currently running in debug mode; the changes made to the package will not take effect until the package is ...
  66. The Package Migration Wizard migrates packages created using the SQL Server 2000 tools and object models to SQL Server 2008. ...
  67. The Package Migration Wizard requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the DTS ...
  68. The package name, {0}, contains characters that are not valid. The following characters are not valid: \ / : . ? " < > | ...
  69. The package path referenced an object that cannot be found: "%1!s!". This occurs when an attempt is made to resolve a package ...
  70. The package was digitally signed, but the signature is not valid. The contents of the package could have been modified by ...
  71. The page %1!s!, object ID %2!s!, index ID %3!s!, partition ID %4!s!, allocation unit ID %5!s! (type %6!s!) has been modified, ...
  72. The parameter "%1!s!" is not the same type as the type it was created with. Drop and recreate the module using a two-part ...
  73. The parameter %1!s! is not supported for non-SQL Server publications. The value specified for this parameter must be %2!s!. ...
  74. The parameter '%1' cannot be specified because at least one publication already exists in this publication database that ...
  75. The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate ...