Bug: Error: 3449 and server restart during DBCC CHECKDB

This is a quick post to let you know about a bug that a few people are hitting when running DBCC CHECKDB. The symptoms are a series of errors in the error log plus SQL Server forcibly shuts itself down and restarts. I’ve heard of people hitting the bug on SQL Server 2014 and SQL Server 2012 SP1.

[Update 2/24/15] Microsoft has confirmed that it’s a bug in 2014 and 2012 and they’re planning a fix for the next CU of both.

[Update 3/18/15] The fix for SQL Server 2012 is in CU5 of SP2 and is described in KB 3044958.

The error log symptoms look something like I show below:

2014-11-18 09:04:15.69 spid64      The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset 0x00001EE6FD8000 in file 'C:\SQLskills\\Company_file2.ndf:MSSQL_DBCC23'. 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.
2014-11-18 09:04:15.72 spid64      Error: 3314, Severity: 17, State: 3.
2014-11-18 09:04:15.72 spid64      During undoing of a logged operation in database 'Company', an error occurred at log record ID (887654:3321:14). 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.
2014-11-18 09:04:34.38 spid64      Error: 831, Severity: 20, State: 1.
2014-11-18 09:04:34.38 spid64      Unable to deallocate a kept page.
2014-11-18 09:04:34.40 spid64      Error: 3449, Severity: 21, State: 1.
2014-11-18 09:04:34.40 spid64      SQL Server must shut down in order to recover a database (database ID 23). 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.

The 665 error is from the snapshot file that DBCC CHECKDB creates hitting an NTFS limitation on the number of file fragments in a sparse file. This causes the snapshot creation to fail. The failure causes the undo of a log record in the snapshot to fail (remember that a database snapshot undergoes crash recovery to make it transactionally consistent). This failure then leads to SQL Server thinking it has to forcibly restart to recover the snapshot database, which is should never do for a snapshot – and that’s the bug.

I’ll update this post as soon as I hear about the builds that the fix is in.

This is a rare bug to hit, but it’s a regression (from builds people are reporting), and you can help yourself to avoid it by:

  • Creating your own database snapshot, on a volume without file-system free space fragmentation, and running DBCC CHECKDB against the snapshot
  • OR, trying to run DBCC CHECKDB when there isn’t a significant amount of change occurring in the database, so the database snapshot doesn’t have to become very large
  • OR, using the backup-copy-restore-check method of running DBCC CHECKDB on a restored backup of the database on another server

Thanks

41 thoughts on “Bug: Error: 3449 and server restart during DBCC CHECKDB

  1. Encountered on two servers running

    Microsoft SQL Server 2012 – 11.0.5532.0 (X64)
    Jul 14 2014 15:00:27
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 (Build 9600: )

  2. Good (or bad?) to know I’m not alone in experiencing this issue! Have seen this on 11.0.5522, and opted for rescheduling workaround until a fix is implemented.

  3. I wonder how ReFS is supposed to become the next default filesystem if they do not support sparse files. It also does not support named streams used for “anonymous” snapshots.

  4. Interesting.
    I very recently had a production server shutdown with very similar log entries but I was not running DBCC CheckDB. The Database in the log messages was TempDB but otherwise the messages were the very similar.

    During undoing of a logged operation in database ‘tempDB’.

    The error occurred when the TempDB T-Log filled a disk. I was in the process of dropping other files to make space on the drive when the service shutdown.

    This SQL 2008R2 Standard Edition (10.50.4000.0) running on Windows Server 2008R2 EE.

  5. We’ve experienced this issue on a data warehouse server running 11.0.5522.0 EE, on Windows 2008 R2 EE.

    The drive on which we’ve most recently seen the error reported was only recently commissioned, there’s a reasonable amount of free space, and the drive reports 0% fragmentation, though I suppose that doesn’t prevent a highly fragmented sparse file from being created in the cracks between files.

    This has forced us to use the backup-copy-restore-check method that you suggested, which is probably a better long-term approach for us in any case.

  6. We encountered the problem also on the following version:
    Microsoft SQL Server 2012 (SP1) – 11.0.3339.0 (X64)
    Jan 14 2013 19:02:10
    Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

  7. Two servers with the same issue :

    Microsoft SQL Server 2012 (SP1) – 11.0.3412.0 (X64) Enterprise Edition: Core-based Licensing (64-bit)
    Windows Server 2008 R2 Enterprise (Service Pack 1) 64 Bit

    Both databases that face this issue are > 1 TB in size (data files).

  8. We get the 665 every week, on a very-high transaction db: 10k – 25k batches/s.

    We use the “backup-copy-restore” workaround.

    SQL Version: 10.50.4321.0

    We DON’T, however, get 3449, nor a reboot. Sounds like we should resist upgrading to 2012 until a fix is released…

  9. Because of sparse file checkdb will also generate 1450 and 17053 and fail. Applying KB967351 and formatting with /L is supposed to fix the problem.

  10. Thanks for posting about this Paul,

    Just seen it for the second consecutive week on 11.0.3000. We’ll be doing a backup-restore in test check strategy until there’s a fix.

  11. It’s happened a couple of times on this instance:

    Microsoft SQL Server 2012 (SP1) – 11.0.3153.0 (X64)
    Jul 22 2014 15:26:36
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

  12. Looks like the space file limitation is 1024K fragments (copied blocks?). I have a couple of databases on 3+ TB where I have solved the problem with error 665 by running checkdb on multi file databases on snapshot with snapshot files spread on several drives to keep fragments below the limit.
    But as I am using SQL server 2008 R2 (build 10.50.6000.34) for these setup I have no dumps.
    But according sqllog snapshot is corrupted:
    Database snapshot ‘xxx_snapshot’ has failed an IO operation and is marked suspect. It must be dropped and recreated.
    And then sql writes in the log about 60 times during the next 2 minutes:
    Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.
    For me it looks like a general limit with snapshot and the reason for connection with Checkdb is because snapshot directly or indirectly are used by Checkdb.

  13. Encountered the same issue on Microsoft SQL Server 2012 – 11.0.5522.0 (X64)
    Jun 17 2014 17:01:31
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (Hypervisor)

  14. Happened for the first time (for me) yesterday on:

    Microsoft SQL Server 2012 (SP1) – 11.0.3128.0 (X64)
    Dec 28 2012 20:23:12
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 (Build 9200: )

  15. Thanks for posting this Paul. We had a similar situation with databases > 1TB. It’s on SQL 2012 SP1 (11.0.3460.0). It initially didn’t shutdown the server. But the error 665 keeps on appearing and is specifically pointing on one of the data files which is < 1TB.
    The workaround is using CheckTable then CheckAlloc but recently it looks like that the error 665 came back and has actually caused the server to shut down this time. We have applied the SP2 lately. Could the error be due to using checktable/checkalloc or is it because some of the latest hotfixes in SP1 were not incorporated in SP2 (yet).

  16. Paul,
    I encountered this issue on Friday while doing the backup of the database which is about 7TB
    and had set the option on Maintenance plan to verify database integrity.
    Would you recommend that I uncheck that option and do a separate checkdb after restore from the .bak file.

    Thanks
    Neena

  17. Hi

    we are working on sql 2012 sp3 cluster setup, but when we run dbcc checkdb the sql services are restarting without causing failover, anyone aware of this issue

  18. HI Paul,

    As always helpful and kind full, Please also elaborate change in dbcc checkdb behaviour in 2014 in details.

    Regards

  19. I’m wondering if this bug can manifest in other ways. We have a SQL 2014 (previously RTM) server that is hanging when DBCC CHECKDB is being run. It hung at least twice before we stopped the DBCCs for a couple months. We applied the latest service pack because that seemed to resolve the issue in development and test, so the version is currently SQL 2014 SP2 CU1 (12.0.5511.0). I can see in the SQL logs where it successfully completes the DBCCs for some of the databases, but then just stops and a multitude of various errors occur. After the instance enters the bad state, the SQL log shows what looks like memory dumps as users try to access it, and the entire server is affected. External processes trying to access server resources get errors like these:

    • TCP Provider: The semaphore timeout period has expired.
    • ERROR MESSAGE: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)[0].Exception.Message
    • A SQL Exception occurred: A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 – The specified network name is no longer available.)
    • There is insufficient system memory in resource pool ‘default’ to run this query. (about 4 hours later)

    There are 16GB memory on the server, and 13.5GB are allocated to SQL. These are all VMWare servers with Windows Standard 2012 R2.

    I have tried restoring all the databases to a development server with the same configuration, but there are no issues there. Since this is a production server, it’s hard to troubleshoot the problem.

    Do you think this is the same bug? I’m not seeing much about it through searches.

    Thank you,

    Tammy

  20. Hi Paul,

    In our Company, on one of the servers we are running a SQL Server 2012 Standard Edition with Service Pack 3 (Microsoft SQL Server 2012 (SP3) (KB3072779) – 11.0.6020.0 (X64) Oct 20 2015 15:36:27 Copyright (c) Microsoft Corporation Standard Edition 64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)).

    SQL Server got shutdown without any notice at 03:41. We got an alert and logged in and found that SQL Server was stopped.

    Everyday at 01:00, we have scheduled a DBCC CHECKDB which takes about 15 seconds on average, which was successful. We found from the error log there were 3449 errors and 9001 errors for the tempdb and other databases.

    As you have mentioned that this was an issue with SQL Server 2012 SP1, but in our case the patch level is SP3.

    Please advise.

    Thank you,
    Ravimohan Kaivar

    Error Log:
    Date,Source,Severity,Message
    05/18/2017 03:41:17,Logon,Unknown,SQL Server cannot accept new connections because it is shutting down. The connection has been closed. [CLIENT: 10.230.48.45]Cannot close event log because there are still event handle users active.
    05/18/2017 03:41:17,Logon,Unknown,Error: 17188 Severity: 16 State: 1.
    05/18/2017 03:41:17,spid81,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3022:17). 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.
    05/18/2017 03:41:17,spid81,Unknown,Error: 3314 Severity: 21 State: 5.
    05/18/2017 03:41:17,spid95,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3016:1). 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.
    05/18/2017 03:41:17,spid95,Unknown,Error: 3314 Severity: 21 State: 5.
    05/18/2017 03:41:17,Logon,Unknown,Login failed for user ‘ProjectWise_Admin’. Only administrators may connect at this time. [CLIENT: 10.230.48.45]
    05/18/2017 03:41:17,Logon,Unknown,Error: 18451 Severity: 14 State: 1.
    05/18/2017 03:41:17,Logon,Unknown,Login failed for user ‘ProjectWise_Admin’. Only administrators may connect at this time. [CLIENT: 10.230.48.45]
    05/18/2017 03:41:17,Logon,Unknown,Error: 18451 Severity: 14 State: 1.
    05/18/2017 03:41:17,spid81,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3022:21). 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.
    05/18/2017 03:41:17,spid81,Unknown,Error: 3314 Severity: 21 State: 3.
    05/18/2017 03:41:17,spid95,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3022:20). 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.
    05/18/2017 03:41:17,spid95,Unknown,Error: 3314 Severity: 21 State: 3.
    05/18/2017 03:41:17,Logon,Unknown,Login failed for user ‘ProjectWise_Admin’. Only administrators may connect at this time. [CLIENT: 10.230.48.45]
    05/18/2017 03:41:17,Logon,Unknown,Error: 18451 Severity: 14 State: 1.
    05/18/2017 03:41:17,Logon,Unknown,Login failed for user ‘ProjectWise_Admin’. Only administrators may connect at this time. [CLIENT: 10.230.48.45]
    05/18/2017 03:41:17,Logon,Unknown,Error: 18451 Severity: 14 State: 1.
    05/18/2017 03:41:17,Logon,Unknown,Login failed for user ‘ProjectWise_Admin’. Only administrators may connect at this time. [CLIENT: 10.230.48.45]
    05/18/2017 03:41:17,Logon,Unknown,Error: 18451 Severity: 14 State: 1.
    05/18/2017 03:41:17,spid81,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:17,spid81,Unknown,Error: 9001 Severity: 21 State: 5.
    05/18/2017 03:41:17,spid95,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:17,spid95,Unknown,Error: 9001 Severity: 21 State: 5.
    05/18/2017 03:41:17,spid81,Unknown,Error during rollback. shutting down database (location: 1).
    05/18/2017 03:41:17,spid81,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3022:21). 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.
    05/18/2017 03:41:17,spid81,Unknown,Error: 3314 Severity: 21 State: 3.
    05/18/2017 03:41:17,spid95,Unknown,Error during rollback. shutting down database (location: 1).
    05/18/2017 03:41:17,spid77,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.
    05/18/2017 03:41:17,spid77,Unknown,SQL Server shutdown has been initiated
    05/18/2017 03:41:17,Server,Unknown,* Short Stack Dump
    05/18/2017 03:41:17,Server,Unknown,* ——————————————————————————-
    05/18/2017 03:41:17,Server,Unknown,* *******************************************************************************
    05/18/2017 03:41:17,Server,Unknown,*
    05/18/2017 03:41:17,Server,Unknown,* Non-yielding Resource Monitor
    05/18/2017 03:41:17,Server,Unknown,*
    05/18/2017 03:41:17,Server,Unknown,* 05/18/17 03:41:17 spid 2136
    05/18/2017 03:41:17,Server,Unknown,* BEGIN STACK DUMP:
    05/18/2017 03:41:17,Server,Unknown,*
    05/18/2017 03:41:17,Server,Unknown,* *******************************************************************************
    05/18/2017 03:41:17,Server,Unknown,***Stack Dump being sent to D:\MSSQL\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt
    05/18/2017 03:41:17,spid77,Unknown,SQL Server must shut down in order to recover a database (database ID 2). 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.
    05/18/2017 03:41:17,spid77,Unknown,Error: 3449 Severity: 21 State: 1.
    05/18/2017 03:41:17,Server,Unknown,**Dump thread – spid = 0 EC = 0x0000000000000000
    05/18/2017 03:41:17,spid81,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:17,spid81,Unknown,Error: 9001 Severity: 21 State: 5.
    05/18/2017 03:41:17,spid95,Unknown,During undoing of a logged operation in database ‘joi_pw_2dp_a’ an error occurred at log record ID (32315:3022:20). 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.
    05/18/2017 03:41:17,spid95,Unknown,Error: 3314 Severity: 21 State: 3.
    05/18/2017 03:41:17,spid77,Unknown,During undoing of a logged operation in database ‘tempdb’ an error occurred at log record ID (284:84851:95). 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.
    05/18/2017 03:41:17,spid77,Unknown,Error: 3314 Severity: 21 State: 3.
    05/18/2017 03:41:16,spid81,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid81,Unknown,Error: 9001 Severity: 21 State: 1.
    05/18/2017 03:41:16,spid77,Unknown,The log for database ‘tempdb’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid77,Unknown,Error: 9001 Severity: 21 State: 5.
    05/18/2017 03:41:16,Server,Unknown,Using ‘dbghelp.dll’ version ‘4.0.5’
    05/18/2017 03:41:16,spid95,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid95,Unknown,Error: 9001 Severity: 21 State: 5.
    05/18/2017 03:41:16,spid92,Unknown,Database joi_pw_2dp_a was shutdown due to error 9001 in routine ‘XdesRMFull::CommitInternal’. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
    05/18/2017 03:41:16,spid97,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid97,Unknown,Error: 9001 Severity: 21 State: 4.
    05/18/2017 03:41:16,spid65,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid65,Unknown,Error: 9001 Severity: 21 State: 4.
    05/18/2017 03:41:16,spid92,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid92,Unknown,Error: 9001 Severity: 21 State: 4.
    05/18/2017 03:41:16,spid54,Unknown,The log for database ‘joi_pw_2dp_a’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    05/18/2017 03:41:16,spid54,Unknown,Error: 9001 Severity: 21 State: 4.
    05/18/2017 03:41:16,spid1s,Unknown,Write error during log flush.
    05/18/2017 03:41:16,spid1s,Unknown,SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
    05/18/2017 03:41:16,spid1s,Unknown,Error: 17053 Severity: 16 State: 1.
    05/18/2017 03:41:16,spid1s,Unknown,Write error during log flush.
    05/18/2017 03:41:16,spid1s,Unknown,SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
    05/18/2017 03:41:16,spid1s,Unknown,Error: 17053 Severity: 16 State: 1.
    05/18/2017 03:41:16,spid1s,Unknown,Write error during log flush.
    05/18/2017 03:41:16,spid1s,Unknown,SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
    05/18/2017 03:41:16,spid1s,Unknown,Error: 17053 Severity: 16 State: 1.
    05/18/2017 03:41:16,spid1s,Unknown,Write error during log flush.
    05/18/2017 03:40:09,spid1s,Unknown,SQLServerLogMgr::LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
    05/18/2017 03:40:09,spid1s,Unknown,Error: 17053 Severity: 16 State: 1.
    05/18/2017 03:41:16,spid25s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL\OLTP\Data\joi_pw_2dp_a.mdf] in database [joi_pw_2dp_a] (7). The OS file handle is 0x00000000000009D0. The offset of the latest long I/O is: 0x0000002018a000
    05/18/2017 03:41:16,spid25s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL\OLTP\Data\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000000A04. The offset of the latest long I/O is: 0x00000000376000
    05/18/2017 03:38:48,spid25s,Unknown,SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [E:\MSSQL\OLTP\Logs\templog.ldf] in database [tempdb] (2). The OS file handle is 0x0000000000000A34. The offset of the latest long I/O is: 0x0000002a8f3600
    05/18/2017 03:30:07,Backup,Unknown,Log was backed up. Database: joi_pw_ofp_a creation date(time): 2017/01/19(12:15:35) first LSN: 63:3863:1 last LSN: 63:3866:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_ofp_a\LOG\JOIN48_joi_pw_ofp_a_LOG_20170518_033007.trn’}). This is an informational message only. No user action is required.
    05/18/2017 03:30:04,Backup,Unknown,Log was backed up. Database: joi_pw_2dp_a creation date(time): 2017/02/28(09:11:52) first LSN: 32233:44292:1 last LSN: 32315:2957:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_2dp_a\LOG\JOIN48_joi_pw_2dp_a_LOG_20170518_033000.trn’}). This is an informational message only. No user action is required.
    05/18/2017 03:30:00,Backup,Unknown,Log was backed up. Database: joi_plot_2dp_a creation date(time): 2017/02/28(09:11:41) first LSN: 142:140:1 last LSN: 142:143:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_plot_2dp_a\LOG\JOIN48_joi_plot_2dp_a_LOG_20170518_033000.trn’}). This is an informational message only. No user action is required.
    05/18/2017 02:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_ofp_a creation date(time): 2017/01/19(12:15:35) first LSN: 63:3861:1 last LSN: 63:3863:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_ofp_a\LOG\JOIN48_joi_pw_ofp_a_LOG_20170518_023001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 02:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_2dp_a creation date(time): 2017/02/28(09:11:52) first LSN: 32233:43873:1 last LSN: 32233:44292:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_2dp_a\LOG\JOIN48_joi_pw_2dp_a_LOG_20170518_023001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 02:30:01,Backup,Unknown,Log was backed up. Database: joi_plot_2dp_a creation date(time): 2017/02/28(09:11:41) first LSN: 142:138:1 last LSN: 142:140:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_plot_2dp_a\LOG\JOIN48_joi_plot_2dp_a_LOG_20170518_023000.trn’}). This is an informational message only. No user action is required.
    05/18/2017 01:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_ofp_a creation date(time): 2017/01/19(12:15:35) first LSN: 63:3848:1 last LSN: 63:3861:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_ofp_a\LOG\JOIN48_joi_pw_ofp_a_LOG_20170518_013001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 01:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_2dp_a creation date(time): 2017/02/28(09:11:52) first LSN: 32233:43393:1 last LSN: 32233:43873:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_2dp_a\LOG\JOIN48_joi_pw_2dp_a_LOG_20170518_013001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 01:30:01,Backup,Unknown,Log was backed up. Database: joi_plot_2dp_a creation date(time): 2017/02/28(09:11:41) first LSN: 142:125:1 last LSN: 142:138:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_plot_2dp_a\LOG\JOIN48_joi_plot_2dp_a_LOG_20170518_013000.trn’}). This is an informational message only. No user action is required.
    05/18/2017 01:00:48,spid51,Unknown,DBCC CHECKDB (joi_pw_ofp_a) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds. Internal database snapshot has split point LSN = 0000003f:00000f10:0001 and first LSN = 0000003f:00000f0e:0001.
    05/18/2017 01:00:47,spid51,Unknown,DBCC CHECKDB (joi_pw_2dp_a) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 45 seconds. Internal database snapshot has split point LSN = 00007de9:0000aa97:0001 and first LSN = 00007de9:0000aa95:0001.
    05/18/2017 01:00:05,spid54,Unknown,DBCC CHECKDB (msdb) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 2 seconds. Internal database snapshot has split point LSN = 000003fb:0000002c:0001 and first LSN = 000003fb:0000002a:0001.
    05/18/2017 01:00:03,spid54,Unknown,DBCC CHECKDB (model) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds. Internal database snapshot has split point LSN = 00000029:000000bc:0001 and first LSN = 00000029:000000ba:0001.
    05/18/2017 01:00:02,spid54,Unknown,DBCC CHECKDB (mssqlsystemresource) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
    05/18/2017 01:00:01,spid51,Unknown,DBCC CHECKDB (joi_plot_2dp_a) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds. Internal database snapshot has split point LSN = 0000008e:00000085:0001 and first LSN = 0000008e:00000083:0001.
    05/18/2017 01:00:01,spid54,Unknown,DBCC CHECKDB (master) WITH all_errormsgs no_infomsgs data_purity executed by BUHLER\U04288 found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds. Internal database snapshot has split point LSN = 000000ea:00000086:0001 and first LSN = 000000ea:00000084:0001.
    05/18/2017 00:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_ofp_a creation date(time): 2017/01/19(12:15:35) first LSN: 63:3845:1 last LSN: 63:3848:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_ofp_a\LOG\JOIN48_joi_pw_ofp_a_LOG_20170518_003001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 00:30:01,Backup,Unknown,Log was backed up. Database: joi_pw_2dp_a creation date(time): 2017/02/28(09:11:52) first LSN: 32233:42985:1 last LSN: 32233:43393:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_pw_2dp_a\LOG\JOIN48_joi_pw_2dp_a_LOG_20170518_003001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 00:30:01,Backup,Unknown,Log was backed up. Database: joi_plot_2dp_a creation date(time): 2017/02/28(09:11:41) first LSN: 142:122:1 last LSN: 142:125:1 number of dump devices: 1 device information: (FILE=1 TYPE=DISK: {‘N:\MSSQL\OLTP\Backup\JOIN48\joi_plot_2dp_a\LOG\JOIN48_joi_plot_2dp_a_LOG_20170518_003001.trn’}). This is an informational message only. No user action is required.
    05/18/2017 00:00:49,spid15s,Unknown,This instance of SQL Server has been using a process ID of 1112 since 11/04/2017 21:37:14 (local) 12/04/2017 00:37:14 (UTC). This is an informational message only; no user action is required.

Leave a Reply

Your email address will not be published. Required fields are marked *

Other articles

Imagine feeling confident enough to handle whatever your database throws at you.

With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.