SQL Server 2012

  1. The BottomCount function returns the last n-item rows of the table expression, ordered in ascending order by the rank expression. ...
  2. The BottomPercent function returns the smallest number of rows in increasing order such that the sum of the rank expression ...
  3. The BottomSum function returns the smallest number of rows in increasing order such that the sum of the rank expression values ...
  4. The BottomSum function returns the smallest number of rows in increasing order such that the sum of the rank expression values ...
  5. The boundary value '{0}' was not recognized as a valid {1} value. Enter the value in a supported string literal datetime ...
  6. The Broker Configuration conversation on dialog handle '%1!s!' closed due to an error. To troubleshoot this problem, investigate ...
  7. The browser has encountered an error while querying the current hierarchy and has been disabled. Click Reconnect to reload ...
  8. The browser is disabled because custom MDX expressions defined in the Advanced tab were not validated due to the following ...
  9. The bucket for event index {0} could not be located, which prevents a FeatureError from being returned for the {1} feature. ...
  10. The buffer for the session properties is too small to hold all the information for the session. If you do not need the session's ...
  11. The buffer manager attempted to push an error row to an output that was not registered as an error output. There was a call ...
  12. The buffer manager cannot create a file to spool a long object on the directories named in the BLOBTempStoragePath property. ...
  13. The buffer manager cannot create a temporary storage file on any path in the BufferTempStoragePath property. There is an ...
  14. The buffer manager could not create a temporary file on the path "%1!s!". The path will not be considered for temporary storage ...
  15. The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. %1!d! buffers ...
  16. The buffer manager failed a memory allocation call for %3!d! bytes, but was unable to swap out any buffers to relieve memory ...
  17. The buffer manager has allocated %1!d! bytes, even though the memory pressure has been detected and repeated attempts to ...
  18. The buffer manager ran out of memory while trying to extend the table of buffer types. This is caused by an out-of-memory ...
  19. The bulk copy (bcp) client has sent a row length of %1!s!. This is not a valid size. The maximum row size is %2!s!. Use a ...
  20. The bulk copy (bcp) client sent a row length of %1!s!. This size is not valid. The minimum row size is %2!s!. Use a supported ...
  21. The bulk data source provider string has a syntax error near character position %1!s!. Expected '%2!s!', but found '%3!s!'. ...
  22. The Bulk Insert operation of SQL Server Destination has timed out. Please consider increasing the value of Timeout property ...
  23. The bulk load failed. The column is too long in the data file for row %1!s!, column %2!s!. Verify that the field terminator ...
  24. The bulk load failed. Unexpected NULL value in data file row %1!s!, column %2!s!. The destination column (%3!s!) is defined ...
  25. The bulk-copying of data from '{0}' has been chosen as a deadlock victim, the operation will be retried in {1} milliseconds. ...
  26. The byte order mark (BOM) value for the file "%1!s!" is 2!4.4X!, but the expected value is 3!4.4X!. The ExpectBOM property ...
  27. The byte order mark (BOM) value for the file is not valid. The ExpectBOM property was set for this file, but the BOM value ...
  28. The cabinet file '[2]' required for this installation is corrupt and cannot be used. This could indicate a network error, ...
  29. The cache directory is not set, and the collector could not get an accessible temporary directory. Assign a cache directory ...
  30. The cache file is damaged, or the file was not created by using the Cache connection manager. Provide a valid cache file. ...
  31. The cache index position, %1!d!, is not valid. For non-index columns, the index position should be 0. For index columns, ...
  32. The cache refresh plan '{0}' cannot be found. The cache refresh plan identifier that is provided to an operation cannot be ...
  33. The cache refresh plan cannot be created or edited because caching is not enabled for the item '{0}'. Do you want to enable ...
  34. The cache window setting is invalid. Specify a positive integer to indicate the number of temporary collection files to keep. ...
  35. The cached patch file "{0}" is missing. The original file for this cached file is "{1}", which can be installed from "{2}", ...
  36. The CALCULATE command controls the aggregation of leaf cells in the cube. If deleted or modified, the data within the cube ...
  37. The CALCULATE command controls the aggregation of leaf cells in the cube. If the CALCULATE command is deleted or modified, ...
  38. The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications ...
  39. The call to sp_MScdc_capture_job by the Capture Job for database '%1!s!' failed. Look at previous errors for the cause of ...
  40. The cancel operation is in progress. It may take a few minutes for the controller and all clients to reach a ready state. ...
  41. The CanProcess method of the component (ID: %1!d!) returned false for all inputs. No further input data can be processed. ...
  42. The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also ...
  43. The Cardinality property for the {0} is One, but the default value Expression for "{1}" returns a set. The default value ...
  44. The cartridge for the '%{datasource}' datasource does not support table-aliasing, but querying a parent-child dimension requires ...
  45. The cartridge generated a statement that is not valid because more than one text statement was generated, the statement was ...
  46. The case dimension should be the same dimension referenced by the key column of the mining model on which the source dimension ...
  47. The case filter for the mining model, '%{model/}' , is invalid. The specified filter expression evaluates to the following ...
  48. The case filter is invalid because the referenced column '%{ColumnName/}' has content type KEY. You cannot filter on a key ...
  49. The case-sensitive or binary collation '%1!s!' cannot be used with the COLLATE_FILENAME option. Change the collation to a ...
  50. The CASELIKELIHOOD_NORMALIZATION_METHOD parameter for the '%{modelname/}' model is not valid. CASELIKELIHOOD_NORMALIZATION_METHOD ...
  51. The cases cache of the model has been cleared by either setting ClearAfterProcessing cache mode or by issuing a direct DMX ...
  52. The catalog backup file '{0}' could not be accessed. Make sure the database file exists, and the SQL Server service account ...
  53. The catalog database is in SharePoint integrated mode. That is no longer supported by this instance of Reporting Services. ...
  54. The catalog protects data using encryption. A key is needed for this encryption. Enter a password to protect the encryption ...
  55. The cell writeback operation cannot be committed, because the '%{measuregroup/}' measure group does not have a write-enabled ...
  56. The cell writeback operation has a non-trivial slice and measure expression, on the '%{measuregroup/}' measure group. Cell ...
  57. The cell writeback operation has a non-trivial slice on the '%{cubedimension/}' dimension, which is not associated with the ...
  58. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' data mining measure group dimension, ...
  59. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' many-to-many measure group dimension, ...
  60. The cell writeback operation has a non-trivial slice on the '%{measuregroupdimension/}' reference measure group dimension, ...
  61. The cell writeback operation has failed because the underlying relational storage has a table whose number of columns differ ...
  62. The cell writeback operation has the non-sum measure named '%{measure/}' as the current coordinate, which is not allowed. ...
  63. The certificate '%1!s!' is not valid for endpoint authentication. The certificate must have a private key encrypted with ...
  64. The certificate and symmetric key used to encrypt project '%1!s!' does not exist or you do not have sufficient permissions. ...
  65. The certificate specified by name in MY store cannot be found (error: %1!s!). This occurs in CPackage::LoadUserCertificateByName. ...
  66. The certificate used by server {0} for authentication is not deployed on server {1}. The Public role will be checked for ...
  67. The certificate, asymmetric key, or private key file is not valid or does not exist; or you do not have permissions for it. ...
  68. The Change Data Capture '%1!s!' job does not exist in the system table 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' ...
  69. The Change Data Capture job table containing job information for database '%1!s!' cannot be found in the msdb system database. ...
  70. The change for the row with article nickname %1!d! (%2), rowguidcol {%3} could not be applied at the destination. Further ...
  71. The changed value in this cell was not recognized as valid. .Net Framework Data Type: {0} Error Message: {1} Type a value ...
  72. The changes contained in the message downloaded from Publisher '%1' will be applied after having collected and displayed ...
  73. The changes exceed the maximum number of parameters allowed. Consider reducing the number of rows to be modified, or use ...
  74. The changes that were uploaded to the Publisher are being discarded since the Subscriber has been marked for reinitialization. ...
  75. The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. ...