SQL Server 2012

  1. The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued ...
  2. The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure ...
  3. The subscription to publication '%1!s!' was not found but a shared agent does exist. To specify a subscription to a publication ...
  4. The subscription to publication '%1' could not be verified. Ensure that all Merge Agent command line parameters are specified ...
  5. The subscription was successfully created. The subscription will be visible the next time you run Windows Synchronization ...
  6. The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and ...
  7. The summation of all expression values in the most precise expression data type. If the expression result is integer, numeric, ...
  8. The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore. ...
  9. The synchronization agent encountered an error and failed to determine if a new snapshot must be applied during the next ...
  10. The synchronization method (@sync_method) must be '[bcp native', '[bcp character', 'concurrent', 'concurrent_c', 'database ...
  11. The syntax for calling out tokens in SQL Server Agent job steps has changed in SQL Server 2005. Instead of using square brackets ...
  12. The syntax for the 'Process' command is incorrect. The 'Bindings' keyword cannot appear under a 'Process' command if the ...
  13. The syntax for the 'Process' command is incorrect. The 'Datasource' keyword cannot appear under a 'Process' command if the ...
  14. The syntax for the 'Process' command is incorrect. The 'DatasourceView' keyword cannot appear under a 'Process' command if ...
  15. The syntax for the 'Process' command is incorrect. The 'ErrorConfiguration' keyword cannot appear under a 'Process' command ...
  16. The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, ...
  17. The syntax for the ImpersonationInfo object is incorrect. The value of the ImpersonationMode property (%{strImpMode/}) is ...
  18. The syntax of argument "/{0}" is incorrect. Either the delimiter '=' is missing or there is one or more space characters ...
  19. The syntax of the broker instance '%1!s!' is invalid. The specified broker instance is too long, the maximum size is 256 ...
  20. The syntax that is used tokens in SQL Server Agent job steps has changed from the syntax that is used in SQL Server 2000. ...
  21. The system databases of the current instance of SQL Server cannot be rebuilt because the SQL Server service startup type ...
  22. The system is out of memory. If using a 32-bit version of the product, consider upgrading to the 64-bit version or increasing ...
  23. The system name '%1!s!' was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying ...
  24. The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically ...
  25. The system reports %1!d! percent memory load. There are %2!s! bytes of physical memory with %3!s! bytes free. There are %4!s! ...
  26. The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary ...
  27. The T-SQL shown here may not necessarily be the exact T-SQL executed at the server due to any conditional logic you configured ...
  28. The table "%1!s!" does not appear to be a valid pre-built match index. This error occurs if the metadata record cannot be ...
  29. The table "{0}" already contains a configuration with name "{1}". Do you want to reuse this configuration or overwrite information ...
  30. The table "{0}" cannot be used as a source for SQL Server configurations. The column "{1}" does not have the expected data ...
  31. The table "{0}" cannot be used as a source for SQL Server configurations. This table does not have the necessary columns ...
  32. The table %1!s! contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it ...
  33. The table %1!s! does not have a primary key, which is required for transactional replication. Create a primary key on the ...
  34. The table %1!s!, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized ...
  35. The table '%1!s!' cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online. ...
  36. The table '%1!s!' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular ...
  37. The table '%1!s!.%2!s!' already appears in a transactional publication on Oracle Gateway Publisher '%3!s!'. When using the ...
  38. The table '%1!s!.%2!s!' already appears in the transactional publication '%3!s!' on Publisher '%4!s!'. The Oracle Gateway ...
  39. The table '%{dimname/}' has two relationships with the same ToRelationshipEnd Role name: '%{rolename/}', which is not allowed. ...
  40. The table '{0}' does not exist in the database '{1}'. Verify spelling of the table and database names and make sure you are ...
  41. The table above shows only those jobs that are still processing on the report server. To cancel all jobs, click OK. To close ...
  42. The Table Analysis Tools Add-in for Excel 2010 cannot function without a connection to a SQL Server 2008 (or later) Analysis ...
  43. The table being loaded into memory has a user-defined data type (' ') that is not recognized. Close all of your open database ...
  44. The table column '%{IWColumnName/}', in the table '%{IWTableName/}', binds to a column of Binary data type, which is not ...
  45. The table definition appears to be missing from the DATATABLE function; the last parameter of the DATATABLE function must ...
  46. The table is linked to an Excel table that is no longer available. The Excel table might have been deleted or renamed. Correcting ...
  47. The table name '{0}' specified through -Tf switch cannot be parsed successfully. Table name should be specified in format: ...
  48. The Table or View name is not expected. If you are quoting the table name, please use the prefix %1!s! and the suffix %2!s! ...
  49. The table or view name is not valid. Please use the table prefix {0} and suffix {1} of the data provider if you are quoting ...
  50. The table that you selected includes one or more columns of type hierarchyid. Publishing this table for bidirectional replication ...
  51. The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution ...
  52. The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. ...
  53. The table {1}' has rows that contain a different number of cells than the number of the columns in the table (including cells ...
  54. The table, '%{IWTableName/}', cannot be created in Tabular mode because the column, '%{IWColumnName/}', is associated with ...
  55. The Table-Valued Parameter column %1!Iu! was bound through multiple accessor bindings. Each Table-Valued Parameter Rowset ...
  56. The Table-Valued Parameter column %1!Iu! was marked as default and it was also bound through accessor %2!Iu!. Default columns ...
  57. The Table-Valued Parameter column %1!Iu! was not bound in the same accessor as it's surrounding columns (from %2!Iu! to %3!Iu!). ...
  58. The Table-Valued Parameter column %1!Iu! was not bound through any accessor binding. Each non-default column must have 1 ...
  59. The Tabular Data Stream (TDS) version 1!s! of the client library used to open the connection is unsupported or unknown. The ...
  60. The tail of the log for database %1!s! is being rewritten to match the new sector size of %2!s! bytes. %3!s! bytes at offset ...
  61. The tail of the log for the database "%1!s!" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if ...
  62. The target '%1!s!' of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT ...
  63. The target '%1!s!' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested ...
  64. The target '%1!s!' of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the ...
  65. The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that ...
  66. The target database ('%1!s!') is in an availability group and currently does not allow read only connections. For more information ...
  67. The target database ('%1!s!') is in an availability group and is currently accessible for connections when the application ...
  68. The target database, '%1!s!', is participating in an availability group and is currently not accessible for queries. Either ...
  69. The Target dimension is based on a mining model built from the Source dimension. The Source dimension must also be included ...
  70. The target file extension '{0}' does not match the source file extension '{1}'. File extensions of .rdl, .rsds, .odc, .rsd, ...
  71. The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), ...
  72. The target selection policy input is invalid. Please check that it has a valid condition and the condition implements 'ServerSelection' ...
  73. The target server cannot establish an encrypted connection to the master server '%s'. Make sure that the MsxEncryptChannelOptions ...
  74. The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information ...
  75. The target table '%1!s!' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause ...