Query to find the last restored date

Here is the query to find the last database restore dates:

SELECT TOP 5 * FROM RESTOREHISTORY WITH (nolock)

WHERE (DESTINATION_DATABASE_NAME = 'Databasename') ORDER BY RESTORE_DATE DESC


Query to find the Original database name and last date restored.\

SELECT
bus
.database_name Org_DBName,

Restored_To_DBNameLast_Date_Restored
FROM
msdb
..backupset bus INNER
JOIN(SELECT  backup_set_id
,

Restored_To_DBName,

Last_Date_Restored

FROM

msdb..restorehistory

INNER JOIN
(
SELECT
rh.destination_database_name Restored_To_DBName,
Max(rh.restore_date) Last_Date_Restored
FROM

msdb..restorehistory rh
GROUP BY

rh.destination_database_name

) AS InnerRest
ON

destination_database_name = Restored_To_DBName AND

restore_date = Last_Date_Restored

)
As RestData
ON
bus
.backup_set_id = RestData.backup_set_id

Query to Find the fragementation of the Table

 Script to find the fragementation of a table and choose the Rebuild or Reorganize the indexes.

SELECT a.index_id, name, avg_fragmentation_in_percent FROM sys.dm_db_index_physical_stats (DB_ID(), OBJECT_ID(N'Table Name'), NULL, NULL, NULL) AS a JOIN sys.indexes AS b ON a.object_id = b.object_id AND a.index_id = b.index_id; GO

For Ex:

USE AdventureWorks2008R2;
GO
SELECT a.index_id, name, avg_fragmentation_in_percent
FROM sys.dm_db_index_physical_stats (DB_ID(), OBJECT_ID(N'Production.Product'),
     NULL, NULL, NULL) AS a
    JOIN sys.indexes AS b ON a.object_id = b.object_id AND a.index_id = b.index_id;
GO

The statement might return a result set similar to the following.

 

index_id    name                        avg_fragmentation_in_percent
----------- --------------------------- ----------------------------
1           PK_Product_ProductID        15.076923076923077
2           AK_Product_ProductNumber    50.0
3           AK_Product_Name             66.666666666666657
4           AK_Product_rowguid          50.0

(4 row(s) affected)

Depends on Fragementation we can reorganize or  rebuld the indexes .

avg_fragmentation_in_percent value

Corrective statement


> 5% and < = 30% 

ALTER INDEX REORGANIZE


> 30%

ALTER INDEX REBUILD WITH (ONLINE = ON)*

* Rebuilding an index can be executed online or offline. Reorganizing an 
index is always executed online. To achieve availability similar to the 
reorganize option, you should rebuild indexes online.

Install SQL Server 2012 Using SysPrep

When installing SQL Server, the Advanced page of the SQL Server Installation Center has two options for preparing a SQL Server install. Using these options allows us to prepare a stand-alone instance of SQL Server and to complete the configuration at a later time. SQL Server SysPrep involves a two-step process to get to a configured stand-alone instance of SQL Server:

• Image preparation of a stand-alone instance of SQL Server
• Image completion of a prepared stand-alone instance of SQL Server

Image Preparation

This step stops the installation process after the product binaries are installed, without configuring the instance of SQL Server that is being prepared. The only features that can be selected during SysPrep installations are the Database Engine and Reporting Services Native Mode. SQL Server Browser and SQL Server Writer are automatically prepared. These are then completed when you complete the SQL Server install by using the Complete Image step. After the completion of the image preparation step, SQL Server is not in a state that it can be used.

Image Completion

This step enables you to complete the configuration of a prepared instance of SQL Server. After this step, the instance is ready to be used.

---

Prepare Image for SQL Server 2012 Using SysPrep

To get started, click on the SQL Server 2012 setup.exe. In the SQL Server Installation Center, navigate to the Advanced page and select "Image preparation of a stand-along instance of SQL Server". Select OK on the Setup Support Rules, if there are no errors.

Accept the License Agreement and select Next.

Click the Install button to install the setup files.

Click Next.

Select the features you want to SysPrep and then click Next. Observe that only the Database Engine Services, SQL Server Replication, Full-Text, and Reporting Services - Native can be installed using SysPrep. In this example we are installing the Database Engine Services only.

Click Next.

Specify an Instance ID (the name of your prepared instance, the default is MSSQLSERVER) and then click Next. This name is then used during the completion stage.

Click Next on the Disk Space Requirements dialog.

Click Next to Prepare Image Rules.

Click Prepare to prepare the SysPrep image.

At this point we have prepared the SysPrep image for the installation of SQL Server 2012.

---

Complete Installation for SQL Server 2012 Using SysPrep

After you go through the prepare stages you will now have another option in the Start menu to complete the installation. To run the complete process, go to Start > Program Files > Microsoft SQL Server 2012 > Complete SQL Server Installation as shown below.

Click OK on the Setup Support Rules.

Click Next.

Specify the edition to be installed or enter a product key. This will determine which version of SQL Server is to be installed for this instance. If you use the Evaluation version this will install the Enterprise Edition which is good for 180 days.

Accept the License Agreement and click Next.

Specify the prepared instance that we want to use for the completion and then click Next. After this is selected we can see the Features, Edition and Version for this prepared instance.

On the Feature Review page, you will see the selected features and components included in the install during the prepare step. We cannot add more features during the Complete Phase. We need to complete the setup and then use Add Features on the Installation Center to add additional features.

Specify an Instance Name for this installation. This can be either a default instance or a named instance and then click Next.

Specify the Service Accounts and Collation information and click Next.

Specify the Authentication Scheme - Windows or Mixed authentication.

Select the directories where SQL data files and log files will be put and click Next.

Click Next to Complete Image Rules validation.

Click on Complete to complete the SQL Server installation using SysPrep.

Now we have a completed SQL Server 2012 installation using SysPrep.

Now we can connect to SQL Server 2012 using Management Studio and can work with it just like a regular SQL Server installation.
If we want to install another instance on this same server we can run through the Complete Installation steps and create a new named instance and change the parameters where needed.

---

Use for SQL Server SysPrep

1. We can prepare one or more unconfigured instances of SQL Server. Each configuration can have different options.
2. We can capture the SQL Server Setup configuration file of a prepared instance and use it to prepare additional unconfigured SQL Server instances on multiple computers for later configuration.
3. In combination with the Windows System Preparation tool (also known as Windows SysPrep); we can create an image of the operating system including the unconfigured prepared instances of SQL Server on the source computer. Later on we can deploy the operating system image to multiple computers. After completing the configuration of the operating system, we can configure the prepared instances by using the Complete Image step for the SQL Server setup.

Limitations

1. Only the database engine and reporting services are supported by SysPrep.
2. It cannot be used for clustering
3. It is not supported on IA64 system or supported in WOW64.
4. The installation media needs to be available when preparing an image and configuring the image. When using SysPrep for SQL Server Express, we need to extract the files to the local machine before preparing the image.

Next Steps

• If you have not had a chance to preview SQL Server 2012, download an eval copy of SQL Server 2012 to start today.
• Review these additional SQL Server Installation Tips

Query to takequtomated table backup

Query to take backup of tables randomly

 

declare @sqlquery nvarchar(4000)

 

set @sqlquery = N'select * into niku.[CMN_SEQ_CMN_EXCHANGE_RATES_bk_' + convert(varchar(8),GETDATE(),112) + '] from niku.[CMN_SEQ_CMN_EXCHANGE_RATES]'

print @sqlquery

execute sp_executesql @sqlquery

query to find the last backup taken

Here is the query to find the last back taken in SQL Server

SELECT
 T1
.Name as DatabaseName,

COALESCE
(Convert(varchar(12), MAX(T2.backup_finish_date), 101),'Not Yet Taken') as LastBackUpTaken,

COALESCE
(Convert(varchar(12), MAX(T2.user_name), 101),'NA') as UserName

FROM
sys.sysdatabases T1 LEFT OUTER JOIN msdb.dbo.backupset T2

ON
T2.database_name = T1.name

GROUP
BY T1.Name

ORDER
BY T1.Name

SQL server login timedout expired

I was unable to login to SQL server : It was throughing an error ,Login timed out expired:

i was  able ping the server, i was able to RDP the server and SQL services were running fine but i was not able to register SQL in SSMS or SQLWB.

I found the problem was with Firewall it seems to be blocked or was not enabled for port 1433.

So i have created an inbound rule for Sql to allow 1433 port for whole domain in Windows firewall advance security.

--> go to Adminstrative tools--> select windows Firewall with advance security ----> create one inbound rule  --> select port and click on next-->select TCP and port number 1433-->select allow connection-->select only to the domain --> Type Name and click on finish .

This fixed my issue and i was able to register  SQL server.

 

SQLAgent.out and SQLagent error log files has filleup the drive

Recently i faced an issue, SQL Agent files (SQLAgent.out,SQLAgent1,SQlAgent2,SQlAgent3,SQlAgent4,SQlAgent5,SQlAgent6,SQlAgent7) has occupied almost whole C Drive(40 GB), so No one was able to RDP and no memory was available and no users were able to run queries or perfrom any transactions.

Ans:

Please make sure take the backup error log files before if you need this for reference in future.

What is the SQL Server Error Log?

SQL Server maintains its own error logs that contain messages describing informational and error events. The SQL Server error log is a great place to find information about what is happening on your database server. Each SQL Server Error log will have all the information related to failures / errors that has occurred since SQL Server was last restarted or since the last time you have recycled the error logs.

By default, there are six achieved SQL Server Error Logs along with the ERRORLOG which is currently used. However, it is a Best Practice to increase the number of SQL Server Error Logs from the default value of six. In this tip, you will see the steps which you need to follow to increase the number of SQL Server Error Logs.

A new SQL Server error log file will be created when one of two things happens:

1. The SQL Server service is started
2. sp_cycle_errorlog is called

Best Practice – SQL Server Error Log

1. Ensure you Error log directory is backed up regularly, with windows OS backup
2. Increase the number of SQL Server Error Logs from the default value of six.
3. Make a schedule job to Recycle the Error on a specified schedule to ensure, you log size in control as large files takes time to read data
4. Check SQL Server Error log on daily basis as all important / critical messages and warnings are logged in SQL Server Error Log

How to specify number of log files to be maintained by SQL Server

SQL Server Management Studio -> Management -> SQL Server Logs
Right click -> Configure

Same way, we can configure the number of SQL Server Agent Logs too.

SQL Server Management Studio -> SQL Server Agent-> Server Logs
Right click -> Configure

How to Start a New SQL Server Error Log

sp_cycle_errorlog, stored procedure is used to recycle the SQL Server error log

How to Start a New SQL Server Agent Log

USE MSDB
GO
EXEC dbo.sp_cycle_agent_errorlog
GO

OR, Agent Log can be cycle graphically also

Notes

1. By default, SQL Server maintains a minimum of 6 Error Log Files.
2. Each time the SQL Server is restarted, the Current Active Log File is recycled and new one created.
3. The Error Log Files are stored in the “Microsoft SQL Server\MSSQL.1\MSSQL\LOG\” Directory.
4. It stores, security related login information, Logins info such as Failure Logins or Failure and Success Logins
5. Error Logs also stores, changes in Database Settings, Database backup related information; both successful backups and failures are reported.
6. If case SQL Services failed to start, SQL Server Error Log is the first thing, which shuld be looked at to figure out the reason, why its failing.
7. sp_cycle_errorlog, can only be executed by members of sysadmins

 

To automate this process across servers, reference the sp_set_sqlagent_properties system stored procedure.  Below outlines a sample execution.

USE [msdb] GO EXEC msdb.dbo.sp_set_sqlagent_properties @errorlogging_level=7 GO

Setting Alerts for SQL Server Critical Errors

Setup Alerts:

As a DBA, we must monitor All SQL Server errors having severity level between 17 to 25. Any errors from level 20 to 25 are serious in nature however for 17 to 19 a DBA involvement is required for resolution. Here is self explanatory MS description of error levels, steps to get automatic alert as soon as any of error occurs and list of error messages.

• 17 Insufficient ResourcesThese messages indicate that the statement caused SQL Server to run out of resources or have exceeded limit set by the database administrator.
• 18 Nonfatal Internal Error DetectedThese messages indicate that there is some type of internal software problem, but the statement finishes, and the connection to SQL Server is maintained.
• 19 Error in ResourceThese messages indicate that some non configurable internal limit has been exceeded and the current batch process is terminated.
• 20 SQL Error in Current Process These messages indicate that a statement has encountered a problem. Because the problem has affected only the current process, it is unlikely that the database itself has been damaged.
• 21 SQL Fatal Error in Database dbid ProcessesThese messages indicate that you have encountered a problem that affects all processes in the current database; however, it is unlikely that the database itself has been damaged.
• 22 SQL Fatal Error Table Integrity SuspectThese messages indicate that the table or index specified in the message has been damaged by a software or hardware problem.
• 23 SQL Fatal Error: Database Integrity SuspectThese messages indicate that the integrity of the entire database is in question because of a hardware or software problem.
• 24,25 Hardware ErrorThese messages indicate some type of media failure. The system administrator might have to reload the database. It might also be necessary to call your hardware vendor.

T-SQL example to create a new Alert for Severity Level 17, including sending email response to Operator named as ‘DBAAlerts’. This code can be used to create alerts for remaining severity levels till 25.


By Script:

USE [msdb]

GO

EXEC msdb.dbo.sp_add_alert @name=N'Sev17', 

        @message_id=0, 

        @severity=17, 

        @enabled=1, 

        @delay_between_responses=600, 

        @include_event_description_in=0, 

        @job_id=N'00000000-0000-0000-0000-000000000000'

GO

EXEC msdb.dbo.sp_add_notification @alert_name=N'Sev17', 

@operator_name=N'DBAALerts', @notification_method = 1

GO

 

Using GUI

 

 As an alternative, you may use SSMS to create Alerts

 

Go to Alerts,

 

Right click & choose New Alert

 

Select Severity :(017--Insufficeient resources)

 

--for dataspace issue

 

 

select Respose TAB,

 

Chcek the Notify operator and Select the DBA ALerts for EMail to recieve ALerts.

 

Message ID,s and importance

 

SQL Server 2008 Contains 294 events/messages having severity level grater than 16(SQL 2005 contains only 230). You may find the list using following T-SQL

 

 

 

severity	message_id	is_event_logged	Text
24	823	1	The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
24	824	1	SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file ‘%ls’.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
24	832	1	A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file ‘%ls’, page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.
24	1459	1	An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it.
24	3628	1	The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator.
24	5125	0	File ‘%ls’ appears to have been truncated by the operating system.  Expected size is %I64d KB but actual size is %I64d KB.
24	5159	0	Operating system error %.*ls on file “%.*ls” during %ls.
24	9015	1	The log record at LSN %S_LSN is corrupted.
24	14265	1	The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and Windows System and Application event logs for possible causes.
24	17405	1	An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
23	211	1	Possible schema corruption. Run DBCC CHECKCATALOG.
23	1457	1	Synchronization of the mirror database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The ALTER DATABASE command failed. Ensure that the principal database, if available, is back up and online, and then reconnect the mirror server instance and allow the mirror database to finish synchronizing.
23	3864	1	Could not find an entry for index with ID %d on object with ID %d in database with ID %d. Possible schema corruption. Run DBCC CHECKDB.
23	5511	0	FILESTREAM’s file system log record ‘%.*ls’ under log folder ‘%.*ls’ is corrupted.
23	5533	0	The FILESTREAM file system log record that has the LSN ‘%d:%d:%d’ is missing. Log folder ‘%.*ls’ is corrupted. Restore the database from a backup.
23	5534	0	SQL log record at LSN ‘%d:%d:%d’ for database ‘%.*ls’ is corrupted.  Database cannot recover.
23	5535	0	FILESTREAM data container ‘%.*ls’ is corrupted.  Database cannot recover.
23	5536	0	FILESTREAM deleted folder ‘%.*ls’ is corrupted.  Database cannot recover.
23	5571	0	Internal FILESTREAM error: failed to access the garbage collection table.
23	5572	0	Internal FILESTREAM error: failed to perform a filesystem operation because of a potential corruption.
23	8440	1	The conversation group exists, but no queue exists.  Possible database corruption.  Run DBCC CHECKDB.
23	8443	1	The conversation with ID ‘%.*ls’ and initiator: %d references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database.
23	8444	1	The service queue structure is inconsistent.  Possible database corruption.  Run DBCC CHECKDB.
23	8461	1	An internal service broker error detected.  Possible database corruption.  Run DBCC CHECKDB.
23	9100	1	Possible index corruption detected. Run DBCC CHECKDB.
23	9657	1	The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware problems. Check the SQL Server error log and the Windows event logs for information on possible hardware problems. Restart SQL Server to rebuild tempdb.
22	669	0	The row object is inconsistent. Please rerun the query.
22	683	0	An internal error occurred while trying to convert between variable-length and fixed-length decimal formats.  Run DBCC CHECKDB to check for any database corruption.
22	684	0	An internal error occurred while attempting to convert between compressed and uncompressed storage formats.  Run DBCC CHECKDB to check for any corruption.
22	685	0	An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
22	913	1	Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.
22	5102	0	Attempted to open a filegroup for the invalid ID %d in database “%.*ls”.
22	5180	1	Could not open File Control Bank (FCB) for invalid file ID %d in database ‘%.*ls’. Verify the file location. Execute DBCC CHECKDB.
22	7105	1	The Database ID %d, Page %S_PGID, slot %d for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE.
22	7108	1	Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
22	8966	1	Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
21	566	1	An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the “-f” switch, and using SP_CONFIGURE.
21	602	1	Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
21	603	1	Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
21	605	1	Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
21	606	1	Metadata inconsistency.  Filegroup id %ld specified for table ‘%.*ls’ does not exist. Run DBCC CHECKDB or CHECKCATALOG.
21	613	0	Could not find an entry for worktable rowset with partition ID %I64d in database %d.
21	615	1	Could not find database ID %d, name ‘%.*ls’. The database may be offline. Wait a few minutes and try again.
21	822	1	Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
21	829	1	Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
21	905	1	Database ‘%.*ls’ cannot be started in this edition of SQL Server because it contains a partition function ‘%.*ls’. Only Enterprise edition of SQL Server supports partitioning.
21	909	1	Database ‘%.*ls’ cannot be started in this edition of SQL Server because part or all of object ‘%.*ls’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.
21	912	0	Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
21	914	0	Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ was aborted before completion. If the abort happened during upgrade of the ‘master’ database, it  will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database  so that the script upgrade steps run to completion.
21	915	0	Unable to obtain the current script level for database ‘%.*ls’. If the error happened during startup of the ‘master’ database, it  will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate  corrective actions and re-start the database so that script upgrade may run to completion.
21	917	0	An upgrade script batch failed to execute for database ‘%.*ls’ due to compilation error. Check the previous error message  for the line which caused compilation to fail.
21	918	0	Failed to load the engine script metadata from script DLL ‘%.*ls’. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error.
21	930	1	Attempting to reference recovery unit %d in database ‘%ls’ which does not exist. Contact Technical Support.
21	931	1	Attempting to reference database fragment %d in database ‘%ls’ which does not exist. Contact Technical Support.
21	932	1	SQL Server cannot load database ‘%.*ls’ because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking.
21	933	1	Database ‘%.*ls’ cannot be started because some of the database functionality is not available in the current edition of SQL Server.
21	934	1	SQL Server cannot load database ‘%.*ls’ because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture.
21	935	1	The script level for ‘%.*ls’ in database ‘%.*ls’ cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached  and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database.
21	1208	1	Could not allocate initial %u lock blocks during startup.  Can not start the server.
21	1209	1	Could not allocate initial %u lock owner blocks during startup.  Can not start the server.
21	1210	1	Unable to allocate lock owner block during lock migration. Server halted.
21	1213	1	Error spawning Lock Monitor thread: %ls
21	1401	1	Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Server service.
21	3151	1	Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online.
21	3301	1	The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database.
21	3302	1	Redoing of logged operations in database ‘%.*ls’ failed to reach end of log at log record ID %S_LSN.  This indicates corruption around log record ID %S_LSN. Restore the database from a full backup, or repair the database.
21	3313	1	During redoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
21	3314	1	During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
21	3315	1	During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database ‘%.*ls’ under transaction %S_XID. Restore a backup of the database, or repair the database.
21	3316	1	During undo of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a full backup, or repair the database.
21	3411	1	Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
21	3413	1	Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems.
21	3417	1	Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
21	3420	1	Database snapshot ‘%ls’ has failed an IO operation and is marked suspect.  It must be dropped and recreated.
21	3431	1	Could not recover database ‘%.*ls’ (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS DTC, restore from a full backup, or repair the database.
21	3437	1	An error occurred while recovering database ‘%.*ls’. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again.
21	3441	1	During startup of warm standby database ‘%.*ls’ (database ID %d), its standby file (‘%ls’) was inaccessible to the RESTORE statement. The operating system error was ‘%ls’. Diagnose the operating system error, correct the problem, and retry startup.
21	3442	1	Recovery of warm standby database ‘%.*ls’ (database ID %d) failed. There is insufficient room in the undo file. Increase the size of the undo file and retry recovery.
21	3443	1	Database ‘%.*ls’ (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.
21	3445	1	File ‘%ls’ is not a valid undo file for database ‘%.*ls (database ID %d). Verify the file path, and specify the correct file.
21	3448	1	Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%.*ls’ (database ID %d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. Restore or repair the database.
21	3449	1	SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
21	3456	1	Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%.*ls’ (database ID %d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the database.
21	3457	1	Transactional file system resource manager ‘%.*ls’ failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.
21	3904	0	Cannot unsplit logical page %S_PGID in object ‘%.*ls’, in database ‘%.*ls’. Both pages together contain more data than will fit on one page.
21	4803	1	The bulk copy (bcp) client has sent a row length of %d. This is not a valid size. The maximum row size is %d. Use a supported client application programming interface (API).
21	4804	1	While reading current row from host, a premature end-of-message was encountered–an incoming data stream was interrupted when the server expected to see more data. The host program may have terminated. Ensure that you are using a supported client application programming interface (API).
21	4807	1	The bulk copy (bcp) client sent a row length of %d. This size is not valid. The minimum row size is %d. Use a supported client application programming interface (API).
21	4894	1	COLMETADATA must be present when using bcp.
21	4895	1	Unicode data is odd byte size for column %d. Should be even byte size.
21	8534	0	The KTM RM for this database, %ls, failed to start: %d.
21	8646	1	Unable to find index entry in index ID %d, of table %d, in database ‘%.*ls’. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.
21	9004	1	An error occurred while processing the log for database ‘%.*ls’.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
21	9014	1	An error occurred while processing the log for database ‘%.*ls’. THe log block version is higher than this server allows.
21	9016	1	An error occurred while processing the log for database ‘%.*ls’. The log block could not be decrypted.
21	14713	0	A management data warehouse cannot be installed to SQL Server Express Edition.
21	19034	1	Cannot start C2 audit trace. SQL Server is shutting down.  Error = %ls
20	21	0	Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
20	204	1	Normalization error in node %ls.
20	427	1	Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.
20	617	1	Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor.
20	801	1	A buffer was encountered with an unexpected status of 0x%x.
20	821	1	Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support.
20	831	0	Unable to deallocate a kept page.
20	920	0	Only members of the sysadmin role can modify the database script level.
20	928	1	During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
20	929	1	Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider.
20	948	1	The database ‘%.*ls’ cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.
20	950	1	Database ‘%.*ls’ cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.
20	959	1	The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
20	1203	1	Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
20	1221	1	The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider.
20	1402	1	Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mirroring partners.
20	1501	1	Sort failure. Contact Technical Support.
20	1509	1	Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support.
20	1511	1	Sort cannot be reconciled with transaction log.
20	1522	1	Sort operation failed during an index build. The overwriting of the allocation page in database ‘%.*ls’ was prevented by terminating the sort. Run DBCC CHECKDB to check for allocation and consistency errors. It may be necessary restore the database from backup.
20	1523	1	Sort failure. The incorrect extent could not be deallocated. Contact Technical Support.
20	1532	1	New sort run starting on page %S_PGID found an extent not marked as shared. Retry the transaction. If the problem persists, contact Technical Support.
20	1533	1	Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction.
20	1534	1	Extent %S_PGID not found in shared extent directory. Retry the transaction. If the problem persists, contact Technical Support.
20	1535	1	Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support.
20	1537	1	Cannot suspend a sort that is not in row input phase.
20	1538	1	Cannot insert a row into a sort when the sort is not in row input phase.
20	1832	0	Cannot attach the file ‘%.*ls’ as database ‘%.*ls’.%.*ls
20	3434	1	Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation.
20	3624	1	A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
20	3625	1	‘%hs’ is not yet implemented.
20	3972	1	Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d.
20	4014	0	A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %d, output error: %d).
20	4068	0	sp_resetconnection was sent as part of a remote procedure call (RPC) batch, but it was not the last RPC in the batch. This connection will be terminated.
20	4077	0	The statement failed because the sql_variant value uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
20	5515	0	Cannot open the container directory ‘%.*ls’ of the FILESTREAM file. The operating system has returned the Windows status code 0x%x.
20	6559	1	Could not find type ID %d in database %.*ls. This is due to a schema inconsistency.
20	7102	1	Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
20	7213	1	The attempt by the provider to pass remote stored procedure parameters to remote server ‘%.*ls’  failed. Verify that the number of parameters, the order, and the values passed are correct.
20	7836	0	A fatal error occurred while reading the input stream from the network. The maximum number of network packets in one request was exceeded. Try using bulk insert, increasing network packet size, or reducing the size of the request. The session will be terminated.
20	7884	1	Violation of tabular data stream (TDS) protocol. This is most often caused by a previous exception on this task. The last exception on the task was error %d, severity %d, address 0x%p. This connection will be terminated.
20	7885	1	Network error 0x%lx occurred while sending data to the client on process ID %d batch ID %d. A common cause for this error is if the client disconnected without reading the entire response from the server. This connection will be terminated.
20	7886	1	A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
20	7887	1	The IPv6 address specified is not supported.  Only addresses that are in their numeric, canonical form are supported for listening.
20	7888	1	The IPv6 address specified is not supported.  The server may not be configured to allow for IPv6 connectivity, or the address may not be in a recognized IPv6 format.
20	7909	0	The emergency-mode repair failed.You must restore from backup.
20	8502	1	Unknown token ’0x%x’ received from Microsoft Distributed Transaction Coordinator (MS DTC) .
20	8504	1	The import buffer for this transaction is not valid.
20	8506	1	Cannot change transaction state from %hs to %hs. The change requested is not valid.
20	8509	1	Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls.
20	8510	1	Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.
20	8512	1	Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs.
20	8513	1	Microsoft Distributed Transaction Coordinator (MS DTC) end transaction acknowledgement failed: %hs.
20	8514	1	Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs.
20	8515	1	Microsoft Distributed Transaction Coordinator (MS DTC) global state is not valid.
20	8517	1	Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls.
20	8521	1	This awakening state is not valid: slept in %hs; awoke in %hs.
20	8522	1	Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
20	8532	0	Error while reading resource manager notification from Kernel Transaction Manager (KTM): %d.
20	8533	0	Error while waiting for communication from Kernel Transaction Manager (KTM): %d.
20	8552	0	RegOpenKeyEx of \”%ls\” failed: %ls.
20	8553	0	RegQueryValueEx of \”%hs\” failed: %ls.
20	8554	0	IIDFromString failed for %hs, (%ls).
20	8558	1	RegDeleteValue of \”%hs\” failed: %ls.
20	8648	1	Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint.
20	9003	1	The log scan number %S_LSN passed to log scan in database ‘%.*ls’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
20	9648	0	The queue ‘%.*ls’ has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider increasing the number of MAX_QUEUE_READERS.
20	16999	1	Internal Cursor Error: The cursor is in an invalid state.
20	17310	1	A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
20	17802	1	The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. The connection has been closed. %.*ls
20	17803	1	There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
20	17805	1	The value in the usertype field of the login record is invalid. The value 0×01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server.%.*ls
20	17806	1	SSPI handshake failed with error code 0x%x while establishing a connection with integrated security; the connection has been closed.%.*ls
20	17807	1	Event ‘%ld’, which was received from the client, is not recognized by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent.
20	17809	1	Could not connect because the maximum number of ‘%ld’ user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.%.*ls
20	17810	1	Could not connect because the maximum number of ‘%ld’ dedicated administrator connections already exists. Before a new connection can be made, the existing dedicated administrator connection must be dropped, either by logging off or ending the process.%.*ls
20	17813	1	The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
20	17827	1	There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
20	17828	1	The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
20	17829	1	A network error occurred while establishing a connection; the connection has been closed.%.*ls
20	17830	1	Network error code 0x%x occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms, network writes %d ms, network reads %d ms, establishing SSL %d ms, negotiating SSPI %d ms, validating login %d ms, including user-defined login processing %d ms.%.*ls
20	17832	1	The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
20	17835	1	Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library.%.*ls
20	17836	1	Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.%.*ls
20	17886	1	The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
20	17892	1	Logon failed for login ‘%.*ls’ due to trigger execution.%.*ls
20	18002	1	Exception happened when running extended stored procedure ‘%.*ls’ in the library ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
20	18055	1	Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support.
20	18056	1	The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
20	18057	1	Error: Failed to set up execution context.
20	18061	1	The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error message.
20	21761	0	Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the script.
20	34101	1	An error was encountered during object serialization operation. Examine the state to find out more details about this error.
19	701	1	There is insufficient system memory in resource pool ‘%ls’ to run this query.
19	925	1	Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
19	1204	1	The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
19	3986	0	The transaction timestamps ran out. Restart the server.
19	4408	1	Too many tables. The query and the views or functions in it exceed the limit of %d tables. Revise the query to reduce the number of tables.
18	565	0	A stack overflow occurred in the server while compiling the query. Please simplify the query.
18	1206	0	The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
18	2809	0	The request for %S_MSG ‘%.*ls’ failed because ‘%.*ls’ is a %S_MSG object.
18	3938	0	The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction.  The transaction will be rolled back.
18	14151	1	Replication-%s: agent %s failed. %s
18	17825	1	Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. Review the error log: the entry listed after this error contains the error code from the network library.
18	17826	1	Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
18	20005	0	%ls: Cannot convert parameter %ls: Resulting colv would have too many entries.
18	21512	0	%ls: The %ls parameter is shorter than the minimum required size.
18	21515	0	Replication custom procedures will not be scripted because the specified publication ‘%s’ is a snapshot publication.
17	802	0	There is insufficient memory available in the buffer pool.
17	845	0	Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
17	957	0	Database ‘%.*ls’ is enabled for Database Mirroring, The name of the database may not be changed.
17	972	0	Could not use database ‘%d’ during procedure execution.
17	1101	1	Could not allocate a new page for database ‘%.*ls’ because of insufficient disk space in filegroup ‘%.*ls’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
17	1105	1	Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
17	1121	0	Space allocator cannot allocate page in database %d.
17	1214	1	Internal Error.  There are too many parallel transactions.
17	1220	0	No more lock classes available from transaction.
17	1453	1	‘%.*ls’, the remote mirroring partner for database ‘%.*ls’, encountered error %d, status %d, severity %d. Database mirroring has been suspended.  Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.
17	1454	1	Database mirroring will be suspended. Server instance ‘%.*ls’ encountered error %d, state %d, severity %d when it was acting as a mirroring partner for database ‘%.*ls’. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.
17	1458	1	The principal copy of the ‘%.*ls’ database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring has been suspended. Try to resolve the error condition, and resume mirroring.
17	1510	0	Sort failed. Out of space or locks in database ‘%.*ls’.
17	1803	0	The CREATE DATABASE statement failed. The primary file must be at least %d MB to accommodate a copy of the model database.
17	1807	0	Could not obtain exclusive lock on database ‘%.*ls’. Retry the operation later.
17	3012	0	VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer.
17	3627	1	New parallel operation cannot be started due to too many parallel operations executing at this time. Use the “max worker threads” configuration option to increase the number of allowable threads, or reduce the number of parallel operations running on the system.
17	3807	0	Create failed because all available identifiers have been exhausted.
17	3966	0	Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient space in tempdb. This transaction was marked as a victim earlier because it may need the row version(s) that have already been removed to make space in tempdb. Retry the transaction
17	3967	1	Insufficient space in tempdb to hold row versions.  Need to shrink the version store to free up some space in tempdb. Transaction (id=%I64d xsn=%I64d spid=%d elapsed_time=%d) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning.
17	3999	1	Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information.
17	4805	0	The front-end tool you are using does not support bulk load from host. Use the supported tools for this command.
17	5128	0	Write to sparse file ‘%ls’ failed due to lack of disk space.
17	5904	1	Unable to issue checkpoint: there are not enough locks available. Background checkpoint process will remain suspended until locks are available. To free up locks, list transactions and their locks, and terminate transactions with the highest number of locks.
17	6610	0	Failed to load Msxmlsql.dll.
17	7201	0	Could not execute procedure on remote server ‘%.*ls’ because SQL Server is not configured for remote access. Ask your system administrator to reconfigure SQL Server to allow remote access.
17	7604	0	Full-text operation failed due to a time out.
17	7606	0	Could not find full-text index for database ID %d, table or indexed view ID %d.
17	7607	0	Search on full-text catalog ‘%ls’ for database ID %d, table or indexed view ID %d with search condition ‘%ls’ failed with unknown result (0x%x).
17	7609	0	Full-Text Search is not installed, or a full-text component cannot be loaded.
17	7622	0	There is not sufficient disk space to complete this operation for the full-text catalog “%ls”.
17	7629	0	Cannot open or query the full-text default path registry key. The full-text default catalog path is invalid.
17	8601	0	Internal Query Processor Error: The query processor could not obtain access to a required interface.
17	8606	0	This index operation requires %I64d KB of memory per DOP. The total requirement of %I64d KB for DOP of %lu is greater than the sp_configure value of %lu KB set for the advanced server configuration option “index create memory (KB)”.  Increase this setting or reduce DOP and rerun the query.
17	8628	1	A time out occurred while waiting to optimize the query. Rerun the query.
17	8630	0	Internal Query Processor Error: The query processor encountered an unexpected error during execution.
17	8631	0	Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it.
17	8632	0	Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
17	8634	0	The query processor received an error from a cluster communication layer.
17	8642	0	The query processor could not start the necessary thread resources for parallel query execution.
17	8645	1	A timeout occurred while waiting for memory resources to execute the query in resource pool ‘%ls’ (%ld). Rerun the query.
17	8649	0	The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator.
17	8651	0	Could not perform the operation because the requested memory grant was not available in resource pool ‘%ls’ (%ld).  Rerun the query, reduce the query load, or check resource governor configuration setting.
17	8657	0	Could not get the memory grant of %I64d KB because it exceeds the maximum configuration limit in workload group ‘%ls’ (%ld) and resource pool ‘%ls’ (%ld).  Contact the server administrator to increase the memory usage limit.
17	8680	0	Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.
17	8902	0	Memory allocation error during DBCC processing.
17	9002	1	The transaction log for database ‘%.*ls’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
17	9917	0	An internal error occurred in full-text docid mapper.
17	15319	0	Error: DBCC DBREPAIR REMAP failed for database ‘%s’ (device ‘%s’).
17	16906	0	Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more.
17	18058	1	Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and resource file in localized directory matches the file under English directory. Also check memory usage.
17	23003	0	The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again.
17	25601	0	The extended event engine is out of memory.
17	25602	0	The %S_MSG, “%.*ls”, encountered a configuration error during initialization.  Object cannot be added to the event session.
17	25603	0	The %S_MSG, “%.*ls”, could not be added.  The maximum number of singleton targets has been reached.
17	25604	0	The extended event engine is disabled.
17	25605	0	The %S_MSG, “%.*ls”, could not be added. The maximum number of packages has been reached.
17	25606	0	The extended event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information about possible related problems.
17	25607	0	The extended event engine has been disabled by startup options.  Features that depend on extended events may fail to start.
17	25699	0	The extended event engine failed unexpectedly while performing an operation.
17	26040	1	Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
17	26042	1	Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
17	26044	1	Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
17	26046	1	Server shared memory provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
17	26050	1	Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening.
17	30028	0	Failed to get pipeline interface for ‘%ls’, resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
17	30029	0	The full-text host controller failed to start. Error: 0x%X.
17	30031	0	A full-text master merge failed on full-text catalog ‘%ls’ in database ‘%.*ls’ with error 0x%08X.
17	30038	0	Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
17	30039	0	Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
17	30045	0	Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
17	30049	0	Fulltext thesaurus internal error (HRESULT = ’0x%08x’)
17	30061	0	The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server after the issue is fixed.
17	30062	0	The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
17	30064	0	SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation.
17	30074	0	The master merge of full-text catalog ‘%ls’ in database ‘%.*ls’ was cancelled.
17	30087	0	Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
17	30089	0	The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically.
17	30093	0	The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a valid state. This can prevent SQL Server from initializing critical system objects. Full-text queries will fail until this issue is resolved. Try stopping SQL Server and any filter daemon host processes and then restarting the instance of SQL Server.
17	30094	0	The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to allocate memory or create tasks. Try restarting the instance of SQL Server.
17	30099	0	Fulltext internal error
17	33201	0	An error occurred in reading from the audit file or file-pattern: ‘%s’. The SQL service account may not have Read permission on the files, or the pattern may be returning one or more corrupt files.
17	33202	0	SQL Server Audit could not write to file ‘%s’.
17	33203	0	SQL Server Audit could not write to the event log.
17	33204	0	SQL Server Audit could not write to the security log.
17	33206	0	SQL Server Audit failed to create the audit file ‘%s’. Make sure that the disk is not full and that the SQL service account has the required permissions to create and write to the file.
17	33207	0	SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log.
17	33208	0	SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
17	33214	0	The operation cannot be performed because SQL Server Audit has not been started.