SQL Server 2012

  1. FOR XML AUTO requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name. ...
  2. FOR XML AUTO requires primary keys to create references for '%1!s!'. Select primary keys, or use BINARY BASE64 to obtain ...
  3. FOR XML could not serialize the data for node '%1!s!' because it contains a character ( 2!s!) which is not allowed in XML. ...
  4. FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%1!s!'. Remove the column, ...
  5. FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%1'. Remove the column, ...
  6. FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%1!s!'. ...
  7. FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%1!s!' declares another XMLTEXT column that is not ...
  8. FOR XML EXPLICIT query contains the invalid column name '%1!s!'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!. format where TAGID ...
  9. FOR XML EXPLICIT query contains the invalid column name '%1'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!. format where TAGID is ...
  10. FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column. ...
  11. FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column. ...
  12. FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%1!s!' to precede element-centric IDREFS/NMTOKEN fields. ...
  13. FOR XML EXPLICIT: ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML or XMLTEXT in '%1'. ...
  14. FOR XML EXPLICIT: XML data type cannot be processed as CDATA in column name '%1'. Consider converting XML to a string type. ...
  15. FOR XML EXPLICIT: XML data types and CLR types cannot be processed as CDATA in column name '%1!s!'. Consider converting XML ...
  16. FOR XML NESTED requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name. ...
  17. FOR XML NESTED requires primary keys to create references for '%1'. Select primary keys, or use BINARY BASE64 to obtain binary ...
  18. Forces a re-read of data and an update of dimension attributes. Flexible aggregations and indexes on related partitions will ...
  19. Forces the algorithm to use the indicated columns as regressors in the regression formula regardless of their importance ...
  20. Forcing re-initialization for article '%1!s!' in publication '%2!s!', the clustered index on indexed view '%3!s!' may have ...
  21. Forecasting Error The degree of the polynomial must be between 1 and 5: (1) Constant, (2) Linear Regression, (3 - 5) Multiple ...
  22. Foreign key '%1!s!' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed ...
  23. Foreign key '%1!s!' creation failed. Only NO ACTION referential update action is allowed for referencing computed column ...
  24. Format "%1!s!" is not supported by Flat File Connection Manager. Supported formats are Delimited, FixedWidth, RaggedRight, ...
  25. Forwarded row mismatch: Object ID %1!s!, partition ID %2!s!, alloc unit ID %3!s! (type %4!s!) page %5!s!, slot %6!s! points ...
  26. Forwarded row referenced by more than one row. Object ID %1!s!, partition ID %2!s!, alloc unit ID %3!s! (type %4!s!), page ...
  27. Found multiple dependent virtual network names for the Windows Failover Cluster Resource '%1!s!'. SQL Server will only listen ...
  28. French, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
  29. freq_interval must be between 1 and 10 (1 = Sunday . 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative ...
  30. FR[ename {SQL | DTS};ParentFolderPath;OldFolderName;NewFolderName Operation. Rename the specified folder on SSIS or SQL Server. ...
  31. Full Crawl must be executed on table or indexed view '%1!s!'. Columns affecting the index have been added or dropped since ...
  32. Full-text catalog '%1!s!' ('%2!s!') in database '%3!s!' ('%4!s!') is low on disk space. Pausing all populations in progress ...
  33. Full-text catalog '%1!s!' ('%2!s!') in database '%3!s!' ('%4!s!') is low on system resources. Any population in progress ...
  34. Full-text catalog cannot be published within a transaction. Please re-run the wizard and specify that the publish operation ...
  35. Full-text catalog import has finished for full-text catalog '%1!s!' in database '%2!s!'. %3!s! fragments and %4!s! keywords ...
  36. Full-text catalogs are imported and ready to serve queries faster than with Rebuild. Note that Import does not use the new ...
  37. Full-text catalogs are rebuilt using the new and enhanced word breakers. Rebuilding indexes can take awhile, and a significant ...
  38. Full-text catalogs are reset. Full-text catalog files are removed, but the metadata for full-text catalogs and full-text ...
  39. Full-text crawl forward progress information for database ID: %1!s!, table ID: %2!s!, catalog ID: %3!s! has been reset due ...
  40. Full-text crawl manager has not been initialized. Any crawl started before the crawl manager was fully initialized will need ...
  41. Full-text crawls for database ID: %1!s!, table ID: %2!s!, catalog ID: %3!s! will be stopped since the clustered index on ...
  42. Full-text index for table or indexed view '%1!s!' cannot be populated because the database is in single-user access mode. ...
  43. Full-text predicates cannot appear in the %1!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or ...
  44. Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. ...
  45. Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality ...
  46. Full-text stoplist '%1!s!' cannot be dropped because it is being used by at least one full-text index. To identify which ...
  47. FullGlobe cannot have internal elements and must be the only object in the instance. Remove any other objects in the same ...
  48. FullGlobe instances cannot be objects in the GeometryCollection. GeometryCollections can contain the following instances: ...
  49. Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase ...
  50. Fulltext predicate references columns from two different tables or indexed views '%1!s!' and '%2!s!' which is not allowed. ...
  51. Function %{funcName/} expects a fully qaulified column reference as argument number %{iArg/}, when it's used within EVALUATE. ...
  52. Function %{funcName/} may not be used in DirectQuery-enabled models. Consider changing the expression of the formula or disabling ...
  53. Function '%1!s!' is not allowed in the %2!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE ...
  54. Function '%1!s!' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...
  55. Function '{0}' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...
  56. Function behavior in the event of ties. Skip - ranks that correspond to elements in ties will be skipped; Dense - all elements ...
  57. Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ...
  58. Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ...
  59. Function signature of "FillRow" method (as designated by SqlFunctionAttribute.FillRowMethodName) does not match SQL declaration ...
  60. Further changes need to be made before the current settings can be saved to the component. Warnings reported by the component ...
  61. Fuzzy Lookup was unable to load the entire reference table into main memory as is required when the Exhaustive property is ...
  62. Fuzzy match performance can be improved if an index is created upon the reference table across all of the specified exact ...
  63. Fuzzy match performance can be improved if the exact join FuzzyComparisonFlags on the input column "%1!s!" are set to match ...
  64. F[ile filespec Loads a package that is saved in the file system as a .dtsx file. The filespec argument specifies the path ...
  65. General Information about an assembly is controlled through the following ' set of attributes. Change these attribute values ...
  66. General Information about an assembly is controlled through the following set of attributes. Change these attribute values ...
  67. General properties This tab displays general object properties. The following properties are available: Created In Database ...
  68. Generate a subject area database, staging area database, and packages that load data from flat files to the staging area ...
  69. Generate a subject area database, staging area database, and packages that load data from the staging area database into ...
  70. GENERATE=1= Set , String Expression , Delimiter ]=Returns a concatenated string created by evaluating a string expression ...
  71. Generating a sort key failed with error 1!8.8X!. The ComparisonFlags are enabled, and generating a sortkey with LCMapString ...
  72. Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.%1!s! ...
  73. Generator This tab allows changing the default parameters of the data generators used in Migration Tester . A list of all ...
  74. Generic user-defined aggregate/operator should not have any generic argument instantiated. The following type '{0}' should ...
  75. Georgian-Modern-Sort-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...