SQL Server 2016

  1. File {0} exists in destination SQL Server and since overwrite option is not set for database ignoring transfer of database ...
  2. File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
  3. File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
  4. File {0} was not found. The file might be missing in sources or misspelled in config.xml (note: file name in config.xml is ...
  5. File {0} was not found. The file might be missing in sources or misspelled in config.xml, or case sensitivity may not be ...
  6. Filegroup '%1!s!' already exists in this database. Specify a different name or remove the conflicting filegroup if it is ...
  7. Filegroup '%1!s!' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. ...
  8. Filegroup '%1!s!' is offline, readonly, or no data file. Full-text population on table '%2!s!' is not resumed. Resume full-text ...
  9. Filegroups with MEMORY_OPTIMIZED_DATA, memory-optimized tables and natively compiled modules are not supported when lightweight ...
  10. Filemark on device '%1!s!' appears not to be aligned. The restore operation will proceed using less efficient I/O. To avoid ...
  11. Filemark on device '%1!s!' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: ...
  12. Files and folders cannot be: - Empty strings - System reserved names, including 'CON', 'AUX', PRN', 'COM1' or 'LPT2' - contain ...
  13. Files are copied from the backup folder to a destination folder by a SQL Server Agent job running on the secondary server ...
  14. FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or ...
  15. FILESTREAM DIRECTORY_NAME '%1!s!' attempting to be set on database '%2!s!' is not unique in this SQL Server instance. Provide ...
  16. FILESTREAM DIRECTORY_NAME '{0}' attempting to be set on database '{1}' is not unique in this SQL Server instance. Provide ...
  17. FILESTREAM feature configuration might be inconsistent. To reset the configuration, use the sp_configure stored procedure. ...
  18. FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration ...
  19. FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have ...
  20. FILESTREAM feature has been disabled. Restart the SQL Server instance in order for the settings to fully take effect. NOTE: ...
  21. FILESTREAM file '%1!s!' cannot be added because its destination filegroup cannot have more than one file. Specifying more ...
  22. FILESTREAM File I/O access is enabled, but no listener for the availability group is created. A FILESTREAM PathName will ...
  23. FILESTREAM File I/O access is enabled. One or more availability groups ('%1!s!') currently do not have a listener. A FILESTREAM ...
  24. FILESTREAM file named with GUID '%1!s!' that belongs to FILESTREAM data file ID 2!s! does not exist or cannot be opened. ...
  25. FILESTREAM is not supported on this instance of SQL Server. FILESTREAM is not supported on versions of SQL Server earlier ...
  26. FILESTREAM must be enabled on the primary node of a failover cluster before it can be enabled on a secondary node. Enable ...
  27. FILESTREAM: effective level = %1!s! (remote access disabled), configured level = %2!s!, file system access share name = '%3!s!'. ...
  28. FILESTREAM: effective level = %1!s! (remote access enabled), configured level = %2!s!, file system access share name = '%3!s!'. ...
  29. FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, ...
  30. FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database ...
  31. FILETABLE_DIRECTORY '%1!s!' attempting to be set on table '%2!s!' is not unique in the database '%3!s!'. Provide a unique ...
  32. FILE_ID will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to ...
  33. Filter '%1!s!' already exists in publication '%2!s!'. Specify a unique name for the @filtername parameter of sp_addmergefilter. ...
  34. Filter queries by date. If you specify a beginning date only, all queries requested on or after this date are considered. ...
  35. Filter, sort, and group expressions, lookup functions, and join conditions, do not support data type {2} in the {0} '{1}'. ...
  36. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is a computed ...
  37. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is compared ...
  38. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is compared ...
  39. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is of a CLR ...
  40. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the filter expression contains a comparison with a literal ...
  41. Filtered index '%1!s!' cannot be created on object '%2!s!' because it is not a user table. Filtered indexes are only supported ...
  42. Filtered statistics '%1!s!' cannot be created on object '%2!s!' because it is not a user table. Filtered statistics are only ...
  43. Find case studies, benchmarking data, news and reviews, trial software downloads, and other information to help you decide ...
  44. Finished compressing segment %d{segment/} of column '%{IMBIColumnId/}' for the '%{IMBITableId/}' table '%{IMBIPartitionId/}' ...
  45. Finnish-Swedish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  46. Finnish-Swedish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  47. Finnish-Swedish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  48. Finnish-Swedish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...
  49. Finnish-Swedish, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort ...
  50. Finnish-Swedish, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort ...
  51. Finnish-Swedish-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  52. Finnish-Swedish-100, case-insensitive, accent-insensitive, kanatype-insensitive, width-sensitive, supplementary characters ...
  53. Finnish-Swedish-100, case-insensitive, accent-insensitive, kanatype-sensitive, width-insensitive, supplementary characters ...
  54. Finnish-Swedish-100, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  55. Finnish-Swedish-100, case-sensitive, accent-insensitive, kanatype-insensitive, width-insensitive, supplementary characters ...
  56. Fired when a file handle we're trying to delete is in use and we don't expect it to be. The typical response is dumping all ...
  57. Fires after the chart element background was drawn. This event is fired for elements like: ChartPicture, ChartArea and Legend. ...
  58. Fires when chart element background must be drawn. This event is fired for elements like: ChartPicture, ChartArea and Legend. ...
  59. Fires when chart element background must be drawn. This event is fired for elements such as ChartPicture, ChartArea, and ...
  60. First attempt to bring a HADR Availability Group resource online failed. SQL Server will retry the operation at regular intervals. ...
  61. First, select the type of destination for the data. Second, click New or OK to create a connection or select an existing ...
  62. First, select the type of source for the data. Second, click New or OK to create a connection or select an existing connection ...
  63. Fixed percentage or number of rows are selected as part of the sample. {0} The selected rows are copied into a new spreadsheet ...
  64. Fi[le filespec Loads a package that is saved in the file system as a .dtsx file. The filespec argument specifies the path ...
  65. Flat File Connection Manager Editor can suggest the data type of columns. You can specify the sample size to use, the data ...
  66. Floating precision number data with the following valid values: -1.79E + 308 through -2.23E - 308, 0 and 2.23E + 308 through ...
  67. Floating precision number data with the following valid values: -3.40E + 38 through -1.18E - 38, 0 and 1.18E - 38 through ...
  68. Folder {0} exists in destination SQL Server and since overwrite option is not set for database ignoring transfer of database ...
  69. Folder {0} has an unsupported attribute ({1}) set. Please resolve this issue by removing the unsupported attribute from the ...
  70. Follow the steps to complete the join statement that defines the relationship between rows in the filtered and joined tables. ...
  71. Following partition files were not saved on disk:'%{FileList/}'; files are expected to be saved during distributed processing. ...
  72. For a .NET Assembly Business Logic Handler, the .NET Assembly name should be the name of a valid assembly in '%1!s!' that ...
  73. For a .NET Assembly Business Logic Handler, the @resolver_info must contain the class name in '%1!s!' that implements the ...
  74. For a heterogeneous publisher, -PublisherDB on the distribution agent command line must be set to the publisher's distribution ...
  75. For a local file, verify that the path and file name are correct. For a remote file, verify that the URL is correct and you ...