SQL Server 2012
- Failed to suspend data movement in database '{2}', which resides on the availability replica '{0}' in the availability group ...
- Failed to take availability group '%1!s!' offline. The Windows Server Failover Clustering (WSFC) service may not be running, ...
- Failed to take the Windows Server Failover Clustering (WSFC) group offline (Error code %1!s!). The WSFC service may not be ...
- Failed to truncate AppendOnlyStorageUnit 1!s!. Will retry next time. This is an informational message only. No user action ...
- Failed to update client runtime statistics with invalid index, runtime index is %1!d!, current index is %2!d!, cookie is ...
- Failed to update database "%1!s!" because the database is read-only. Please contact your Azure service owner. There may be ...
- Failed to update SQL Server Network Interfaces registry settings to enable local connectivity using MDAC or WDAC. Instance ...
- Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover ...
- Failed to validate sequence number of the configuration of availability group '%1!s!'. The in-memory sequence number does ...
- Failed to validate the Cyclic Redundancy Check (CRC) of the configuration of availability group '%1!s!'. The operation encountered ...
- Failed to verify the Authenticode signature of '%1!s!'. Signature verification of SQL Server DLLs will be skipped. Genuine ...
- Failed to wait for completion of file requests from the '%1!s!' primary database for the local secondary database. Resuming ...
- Failing over database mirroring will swap the roles of the mirror and principal databases. The mirror database will become ...
- Failing over to this replica will result in changing the failover mode for the primary replica of this availability group. ...
- Failover of the availability group '%1!s!' to the local replica failed because the availability group resource did not come ...
- Failure to read Metadata information from a Table-Valued Parameter Rowset. Failure occurred while attempting to obtain Ordinals ...
- Failure to read Metadata information from a Table-Valued Parameter Rowset. The call to "%1" method on the TVP Rowset object ...
- Failure while loading back a swapped bufer. It may mean the system is in a low memory state and the buffer cannot get its ...
- FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and ...
- FCB::SetSize dbid %1!s! fileid %2!s! oldSize %3!s! newSize %4!s!. To prevent this informational message from appearing in ...
- FC[reate {SQL | DTS};ParentFolderPath;NewFolderName Operation. Create a folder on SSIS or SQL Server. The ParentFolderPath ...
- FDe[lete {SQL | DTS};ParentFolderPath;FolderName Operation. Delete a folder on SSIS or SQL Server. The ParentFolderPath is ...
- FDi[rectory {SQL | DTS}[;FolderPath[;S Operation. List the contents (folders and packages) in a folder on SSIS or SQL Server. ...
- Feature or option "%1!s!" breaches containment in a contained database. Please see Books Online topic Understanding Contained ...
- Feature setting {0} has no MsiScenarios nor ConfigScenarios specified. It is an authoring problem because the setting would ...
- Federation member metadata for a database cannot be changed when there are logically filtered secondaries attached (split ...
- FE[xists {SQL | DTS};FolderPath Operation. Check if a folder exists on SSIS or SQL Server. FolderPath is the path and name ...
- Field with name {0}, but different type already exists in the {1}'s field collection. Field type is {2}, but data type is ...
- File "%1!s!" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause ...
- File "%1!s!" cannot be restored over the existing "%2!s!". Reissue the RESTORE statement using WITH REPLACE to overwrite ...
- File "{0}" already exists. Do you want to reuse this file as the configuration file or overwrite the file with new configuration ...
- File %1!s! in database %2!s! has been set to sparse by the file system but does not belong to a database snapshot. The file ...
- File '%1!s!' appears to have been truncated by the operating system. Expected size is %2!s! KB but actual size is %3!s! KB. ...
- File '%1!s!' cannot be reused until after the next BACKUP LOG operation. If the database is participating in an availability ...
- File '%1!s!' has been rolled forward to LSN %2!s!. This log terminates at LSN %3!s!, which is too early to apply the WITH ...
- File '%1!s!' is claimed by '%2!s!'(%3!s!) and '%4!s!'(%5!s!). The WITH MOVE clause can be used to relocate one or more files. ...
- File '%1!s!' is not a valid undo file for database '%2!s! (database ID %3!s!). Verify the file path, and specify the correct ...
- File '%1' already exists. If this error occurs, locate this file in the Web synchronization directory, delete the file, and ...
- File '%{fileName/}' specified in Restore command is AS encrypted backup file that was created by earlier prerelease of SQL ...
- File Control Bytes/sec shows the overall rate at which bytes are transferred for all file system operations that are neither ...
- File ID %1!s! of database ID %2!s! cannot be shrunk as the target shrink size (%3!s! KB) is greater than the actual file ...
- File ID %1!s! of database ID %2!s! cannot be shrunk to the expected size. The high concurrent workload is leading to too ...
- File not found: {0}. To perform this action SQL Server Configuration Manager component needs to be installed on local machine. ...
- File {0} exists in destination SQL Server and since overwrite option is not set for database ignoring transfer of database ...
- File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
- File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
- File {0} was not found. The file might be missing in sources or misspelled in config.xml (note: file name in config.xml is ...
- File {0} was not found. The file might be missing in sources or misspelled in config.xml, or case sensitivity may not be ...
- Filegroup '%1!s!' already exists in this database. Specify a different name or remove the conflicting filegroup if it is ...
- Filegroup '%1!s!' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. ...
- Filegroup '%1!s!' is offline, readonly, or no data file. Full-text population on table '%2!s!' is not resumed. Resume full-text ...
- Filemark on device '%1!s!' appears not to be aligned. The restore operation will proceed using less efficient I/O. To avoid ...
- Filemark on device '%1!s!' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: ...
- Files and folders cannot be: - Empty strings - System reserved names, including 'CON', 'AUX', PRN', 'COM1' or 'LPT2' - contain ...
- Files are copied from the backup folder to a destination folder by a SQL Server Agent job running on the secondary server ...
- FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or ...
- FILESTREAM DIRECTORY_NAME '%1!s!' attempting to be set on database '%2!s!' is not unique in this SQL Server instance. Provide ...
- FILESTREAM DIRECTORY_NAME '{0}' attempting to be set on database '{1}' is not unique in this SQL Server instance. Provide ...
- FILESTREAM feature configuration might be inconsistent. To reset the configuration, use the sp_configure stored procedure. ...
- FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration ...
- FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have ...
- FILESTREAM feature has been disabled. Restart the SQL Server instance in order for the settings to fully take effect. NOTE: ...
- FILESTREAM file '%1!s!' cannot be added because its destination filegroup cannot have more than one file. Specifying more ...
- FILESTREAM File I/O access is enabled, but no listener for the availability group is created. A FILESTREAM PathName will ...
- FILESTREAM File I/O access is enabled. One or more availability groups ('%1!s!') currently do not have a listener. A FILESTREAM ...
- FILESTREAM file named with GUID '%1!s!' that belongs to FILESTREAM data file ID 2!s! does not exist or cannot be opened. ...
- FILESTREAM is not supported on this instance of SQL Server. FILESTREAM is not supported on versions of SQL Server earlier ...
- FILESTREAM must be enabled on the primary node of a failover cluster before it can be enabled on a secondary node. Enable ...
- FILESTREAM: effective level = %1!s! (remote access disabled), configured level = %2!s!, file system access share name = '%3!s!'. ...
- FILESTREAM: effective level = %1!s! (remote access enabled), configured level = %2!s!, file system access share name = '%3!s!'. ...
- FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, ...
- FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database ...
- FILETABLE_DIRECTORY '%1!s!' attempting to be set on table '%2!s!' is not unique in the database '%3!s!'. Provide a unique ...
- FILE_ID will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to ...
- Filter '%1!s!' already exists in publication '%2!s!'. Specify a unique name for the @filtername parameter of sp_addmergefilter. ...