SQL Server 2016

  1. The Microsoft Time Series algorithm analyzes time-related data to discover patterns based on time series analysis, such as ...
  2. The Microsoft Time Series algorithm uses a combination of ARIMA analysis and linear regression based on decision trees to ...
  3. The Microsoft Windows HTTP Services (WinHTTP) returned error code %1!d!. Unable to find a message in WinHTTP module corresponding ...
  4. The minimum score or the confidence level that will be used by DQS for automatically correcting a term during the automated ...
  5. The minimum score or the confidence level that will be used by DQS for suggesting replacements for a term during the automated ...
  6. The minimum space required for the temporary objects is proportional to the size of the input dataset. Additional space beyond ...
  7. The minimum storage space required for the existing physical design structures (PDS) you have selected to keep is larger ...
  8. The minimum storage space required for the selected physical design structures exceeds the default storage space selected ...
  9. The MINIMUM_ITEMSET_SIZE parameter for the '%{modelname/}' model is not valid. MINIMUM_ITEMSET_SIZE must be between 1 and ...
  10. The MINIMUM_PROBABILITY parameter for the '%{modelname/}' model is not valid. MINIMUM_PROBABILITY must be between 0 and 1. ...
  11. The MINIMUM_SUPPORT parameter for the '%{modelname/}' model is not valid. MINIMUM_SUPPORT must be greater than or equal to ...
  12. The MINIMUM_SUPPORT parameter is negative in the '%{modelname/}' Microsoft Sequence Clustering model. MINIMUM_SUPPORT must ...
  13. The mining model , '%{name/}' is already trained and does not support incremental updates. Before using the INSERT INTO statement, ...
  14. The mining model cannot be added as a temporary model because the '{0}' mining structure is not temporary. Temporary models ...
  15. The mining model content you are currently viewing appears to be out of date. Would you like to refresh the mining model ...
  16. The mining model must be added as a temporary model because the '{0}' mining structure is temporary. Only temporary models ...
  17. The mining structure , '%{name/}' is already trained and does not support incremental updates. Before using the INSERT INTO ...
  18. The mining structure, '{0}', has a holdout greater than 0, therefore the '{1}' algorithm cannot be used in new mining models. ...
  19. The MINING_MODEL_CONTENT schema rowset describes the patterns that were discovered when the mining models were processed. ...
  20. The MINING_MODEL_XML schema rowset contains, in an XML format, the patterns that were discovered when the mining models were ...
  21. The MINING_SERVICE_PARAMETERS schema rowset identifies the parameters that can be used to create models for each type of ...
  22. The MinSimilarity threshold property on the Fuzzy Lookup transformation must be a value greater than or equal to 0.0 but ...
  23. The mirror and witness server instances cannot be the same instance of SQL Server. Select another instance as the witness ...
  24. The mirror database, "%1!s!", has insufficient transaction log data to preserve the log backup chain of the principal database. ...
  25. The mirroring connection to "%1!s!" has timed out for database "%2!s!" after %3!s! seconds without a response. Check the ...
  26. The Mirroring safety mode for database {0} is not set to FULL. Service Broker only supports FULL safety level for Mirroring ...
  27. The MISSING_VALUE_SUBSTITUTION parameter for the mining model, '%{modelname/}', has a value that is not valid. Valid settings ...
  28. The MISSING_VALUE_SUBSTITUTION parameter for the mining model, '%{modelname/}', is not valid. Supported choices are None, ...
  29. The model cannot be changed to DirectQuery mode because data source {0} is of an unsupported type. Delete all tables that ...
  30. The model cannot be changed to DirectQuery mode because it has multiple data sources. Delete all but one data source and ...
  31. The model cannot be changed to DirectQuery mode because table {0} is a calculated table. Delete table {0} from the model, ...
  32. The model cannot be changed to DirectQuery mode because the version of SQL Server used by data source {0} is not supported. ...
  33. The model does not have a shared data source associated with it. Please use the Manage Data Sources menu item to set the ...
  34. The model filter predicate is invalid at (line %d{Line/}, column %d{Column/}). A filter predicate must compare a structure ...
  35. The model of the processor on the system does not support creating %1!s!. This error typically occurs with older processors. ...
  36. The model, '%s{modelname/}', is not valid in the current procedure call because the model does not belong to the mining structure, ...
  37. The model, '%s{modelname/}', is not valid in the current procedure call because the model has Key Time or Key Sequence columns. ...
  38. The MODELLING_CARDINALITY parameter for the '%{modelname/}' model is not valid. MODELLING_CARDINALITY must be greater than ...
  39. The modification made to the collection lead to an invalid Selection state. Please check the SelectionMode to allow zero ...
  40. The module '%1!s!' depends on the missing object '%2!s!'. The module will still be created; however, it cannot run successfully ...
  41. The module being executed is not trusted. Either the owner of the database of the module needs to be granted authenticate ...
  42. The module cannot be merged because it excludes, or is excluded by, another module in the database. Module keys: "{0}". Database ...
  43. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility ...
  44. The monitor server instance is where status and history of log shipping activity for this primary database are recorded. ...
  45. The mount point disk resource '{0}' mounted at '{1}' could not be brought online. The disk must be online in order for the ...
  46. The mount point disk resource '{0}' mounted at '{1}' has a dependency on another resource. To use a disk in a new SQL Server ...
  47. The mount point disk resource '{0}' mounted at '{1}' is already in use. To use a disk in a new SQL Server failover cluster ...
  48. The mount point disk volume '{0}' mounted at '{1}' is not a clustered resource.To continue, add the resource to the cluster, ...
  49. The MoveToRoot property cannot be set to True for this dimension writeback operation, because only parent attributes can ...
  50. The MSCS cluster has been validated but there are warnings in the MSCS cluster validation report, or some tests were skipped ...
  51. The MSDTC is not installed. Some features of SQL Server will fail when clustered if the MSDTC service is not installed. MSDTC ...
  52. The MSDTC service is not running on computer {0}. Some SQL Server features require the MSDTC service. If MSDTC is clustered, ...
  53. The msmdsrv.exe file is the program executable of the Analysis Services instance that loads, queries, and processes PowerPivot ...
  54. The msmdsrv.exe file is the program executable of the Analysis Services instance that loads, queries, and processes PowerPivot ...
  55. The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and Windows System and Application event ...
  56. The multidimensional model contains objects that cannot be expressed in a tabular view. Cannot create table '%{tablename/}', ...
  57. The multidimensional model contains objects that cannot be expressed in a tabular view. The measure '%{measure/}' is already ...
  58. The multiplicity '{0}' on End '{1}' in the conceptual side Association '{2}' doesn't match with multiplicity '{3}' on end ...
  59. The MustUnderstand attribute contained the prefix '{0}' which cannot be converted to be compatible with SQL Server 2014 Reporting ...
  60. The MustUnderstand attribute contained the prefixes '{0}' which cannot be converted to be compatible with SQL Server 2014 ...
  61. The name "%1!s!" given for property "%2!s!" is not a valid SQL identifier name. This error occurs if the name for the property ...
  62. The name "%1!s!" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) ...
  63. The name "{name}" is not valid. Names must not contain any of the following characters: {restrictedCharacters}. Names must ...
  64. The name '%{name/}' is not valid for the %{typename/} because it contains one or more invalid characters (%{invalidchars/}). ...
  65. The name '{0}' does not comply with XEvent naming rules. Names must be less than {1} characters and may not contain " " or ...
  66. The name '{0}' is ambiguous. '{0}' is defined in both the '{1}' namespace and the '{2}' namespace. To disambiguate, either ...
  67. The name column of the '%{property/}' attribute has '%{collation/}' collation. This collation is either not valid or is not ...
  68. The name is not valid. The name cannot consist exclusively of dots or spaces, and the name cannot contain any one of the ...
  69. The name of a file containing the list of tables to be tuned. Tables listed within the file must appear on separate lines, ...
  70. The name of a report item that is the target of the document map label. This report item must be contained directly within ...
  71. The name of a table or file where Database Engine Tuning Advisor writes log messages that occurred during tuning. The table ...
  72. The name of the directory under which FILESTREAM files are shared for the Server. Use SQL Server Configuration Manager to ...
  73. The name of the internal resource must be specified when the 'Get' report server command is used. Verify that the internal ...
  74. The name of the item '{0}' is not valid. The name must be less than {1} characters long. The name must not start with a slash ...
  75. The name of the item is too long. The combined length of the item name and its parent folders must be less than {maxNameLength} ...