SQL Server 2016

  1. Full-text catalog '%1!s!' ('%2!s!') in database '%3!s!' ('%4!s!') is low on disk space. Pausing all populations in progress ...
  2. Full-text catalog '%1!s!' ('%2!s!') in database '%3!s!' ('%4!s!') is low on system resources. Any population in progress ...
  3. Full-text catalog cannot be published within a transaction. Please re-run the wizard and specify that the publish operation ...
  4. Full-text catalog import has finished for full-text catalog '%1!s!' in database '%2!s!'. %3!s! fragments and %4!s! keywords ...
  5. Full-text catalogs are imported and ready to serve queries faster than with Rebuild. Note that Import does not use the new ...
  6. Full-text catalogs are rebuilt using the new and enhanced word breakers. Rebuilding indexes can take awhile, and a significant ...
  7. Full-text catalogs are reset. Full-text catalog files are removed, but the metadata for full-text catalogs and full-text ...
  8. Full-text crawl forward progress information for database ID: %1!s!, table ID: %2!s!, catalog ID: %3!s! has been reset due ...
  9. Full-text crawl manager has not been initialized. Any crawl started before the crawl manager was fully initialized will need ...
  10. Full-text crawls for database ID: %1!s!, table ID: %2!s!, catalog ID: %3!s! will be stopped since the clustered index on ...
  11. Full-text index for table or indexed view '%1!s!' cannot be populated because the database is in single-user access mode. ...
  12. Full-text predicates cannot appear in the %1!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or ...
  13. Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. ...
  14. Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality ...
  15. Full-text stoplist '%1!s!' cannot be dropped because it is being used by at least one full-text index. To identify which ...
  16. FullGlobe cannot have internal elements and must be the only object in the instance. Remove any other objects in the same ...
  17. FullGlobe instances cannot be objects in the GeometryCollection. GeometryCollections can contain the following instances: ...
  18. Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase ...
  19. Fulltext predicate references columns from two different tables or indexed views '%1!s!' and '%2!s!' which is not allowed. ...
  20. full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must be specified if @scheduling_option ...
  21. full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must not be specified if @scheduling_option ...
  22. Function %{funcName/} expects a fully qaulified column reference as argument number %{iArg/}, when it's used within EVALUATE. ...
  23. Function %{funcName/} may not be used in DirectQuery-enabled models. Consider changing the expression of the formula or disabling ...
  24. Function '%1!s!' cannot be used in the definition of BLOCK security predicates. Modify the BLOCK security predicates for ...
  25. Function '%1!s!' is not allowed in the %2!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE ...
  26. Function '%1!s!' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...
  27. Function '%{funcName/}' does not support comparing values of type %{type1/} with values of type %{type2/}. Consider using ...
  28. Function '%{funcName/}' scalar expressions have to be Aggregation functions over CurrentGroup(). The expression of each Aggregation ...
  29. Function '{0}' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...
  30. Function '{0}' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...
  31. Function '{0}' with the same {1} space type parameters already exists. Make sure that function overloads are not ambiguous. ...
  32. Function behavior in the event of ties. Skip - ranks that correspond to elements in ties will be skipped; Dense - all elements ...
  33. Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ...
  34. Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ...
  35. Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ...
  36. Function metadata used in DbFunctionExpression must allow composition. Non-composable functions or functions that include ...
  37. Function signature of "FillRow" method (as designated by SqlFunctionAttribute.FillRowMethodName) does not match SQL declaration ...
  38. Function SubstituteWithIndex() detected more than one row in the index table matching to the current row of the original ...
  39. Functions listed in the provider manifest that are attributed as NiladicFunction='true' cannot have parameter declarations. ...
  40. Further changes need to be made before the current settings can be saved to the component. Warnings reported by the component ...
  41. Fuzzy Lookup was unable to load the entire reference table into main memory as is required when the Exhaustive property is ...
  42. Fuzzy match performance can be improved if an index is created upon the reference table across all of the specified exact ...
  43. Fuzzy match performance can be improved if the exact join FuzzyComparisonFlags on the input column "%1!s!" are set to match ...
  44. F[ile filespec Loads a package that is saved in the file system as a .dtsx file. The filespec argument specifies the path ...
  45. GaugePanel '{0}' StateIndicator '{1}' IndicatorState '{2}' IndicatorStyle value '{3}' was detected in the report. SQL Server ...
  46. GaugePanel '{0}' StateIndicator '{1}' IndicatorState '{2}' IndicatorStyle value '{3}' was replaced by '{4}'. SQL Server 2014 ...
  47. GaugePanel '{0}' StateIndicator '{1}' IndicatorStyle value '{2}' was detected in the report. SQL Server 2014 Reporting Services ...
  48. GaugePanel '{0}' StateIndicator '{1}' IndicatorStyle value '{2}' was replaced by '{3}'. SQL Server 2014 Reporting Services ...
  49. General Information about an assembly is controlled through the following ' set of attributes. Change these attribute values ...
  50. General Information about an assembly is controlled through the following set of attributes. Change these attribute values ...
  51. Generate a subject area database, staging area database, and packages that load data from flat files to the staging area ...
  52. Generate a subject area database, staging area database, and packages that load data from the staging area database into ...
  53. GENERATE=1= Set , String Expression , Delimiter ]=Returns a concatenated string created by evaluating a string expression ...
  54. Generating a sort key failed with error 1!8.8X!. The ComparisonFlags are enabled, and generating a sortkey with LCMapString ...
  55. Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.%1!s! ...
  56. Georgian-Modern-Sort-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  57. Georgian-Modern-Sort-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  58. Georgian-Modern-Sort-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  59. Georgian-Modern-Sort-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  60. Georgian-Modern-Sort-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  61. Georgian-Modern-Sort-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  62. Georgian-Modern-Sort-100, case-insensitive, accent-sensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  63. Georgian-Modern-Sort-100, case-insensitive, accent-sensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  64. Georgian-Modern-Sort-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  65. Georgian-Modern-Sort-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  66. Georgian-Modern-Sort-100, case-sensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  67. Georgian-Modern-Sort-100, case-sensitive, accent-insensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  68. Georgian-Modern-Sort-100, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  69. Georgian-Modern-Sort-100, case-sensitive, accent-sensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  70. Georgian-Modern-Sort-100, case-sensitive, accent-sensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  71. Georgian-Modern-Sort-100, case-sensitive, accent-sensitive, kanatype-sensitive, width-sensitive, supplementary characters ...
  72. German-PhoneBook, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  73. German-PhoneBook-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  74. German-PhoneBook-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  75. German-PhoneBook-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...