SQL Server Data Lost on User DB's

  • I'm facing a very complex situation with my software databases on a specific server. This is the second time this problem happend on this server. Basically while user where working on the system, with no apparently reason, all the data from three user databases where lost.

    The 3 databases where put on a previuos state from 1.5 month ago where all the databases changes made to this databases are lost, yes LOST! I had to restore a backup for all the databases but the data from passed two dates after the last backup where lost. The first time this happend, was with SQL Server Express 2008. Now happends on SQL Server 2008 R2 Standard.

    I suspect a hardware / OS (Hard drive, RAM, etc) problem with the server itself, but no other data where lost (data files, etc) on SQL Server data.

    The only lead i have to discover what happend is the Sql Server LOG, where i see some strange entrys:

    1) All the log previous to 06/08/2015 11:55 (the exact moment where the problem apear) is lost.

    2) An error during decryption, which don't know what it means.

    3) A "Recovery complete" message

    4) After that I see on the log constant message from CHECKDB over my users database (a lot of them) wich no one execute.

    Does anyone have any idea of what could be hapenning here?

    Is this a Hardware issue like I suspect?

    Thanks!

  • Not seeing your specific issues, it doesn't quite sound like a hardware issue. A series of DBCC commands must be coming from somewhere. That's not something that a failing disk will cause. The recovery statement suggests a database that was offline. Whether due to a server restart or a restore operation or some other operation, again, I can't see, so I can't guess, but that one could be somewhat related to a hardware problem. It sounds like someone, or possibly some piece of software, is doing something there.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • First, I think you need to slow down and carefully post what happened and what you've seen. There are a few items that don't make sense. When you say database changes, do you mean the changes to data? Be clear. What is the "log previous to xxx". Do you mean transaction log backups? Or something else? Where are these errors?

    Second, Grant has some good advice here. I think you're listing lost of items without understanding how well SQL Server works.

    If the databases are set to a state where the data was "as of" a point in the past, then likely you have had a restore take place. The recovery complete message points to this as well. I would guess either you have someone restoring over the wrong databases, or a process scheduled(or set up) that shouldn't be running.

    DBCC must be running from somewhere. I would suggest you set up some Extended Events sessions on the server to look for DBCC and restore.

    This isn't likely a hardware issue.

  • First, Thank you very much Grant and Steve for your help, and trying to undestand my problem. Sorry for the rush, but this a serious problem for me and i need to find what cause this problem. I will try to describe the problem, step by step.

    I have 3 user databases running on SQL Server 2008 R2 standard over a Windows 2003 Server. I don't administrate the server itself. Only install SQL Server and attach the databases. I'm a software developer, and my sofware use this databases for data store.

    Everything was working fine, when surprisely at 12am a user tell me that the data he enters in the software that same date is gone.

    So I go to SQL Server and to my surprise see that the main table has only two records when it should have at least 100. I continued searching and see that all the changes I did to the database en the past month (fields added to tables, views i created, stored procedures, etc) are missing. It's like someone restore and old backup or i gigantic transaction with all the changes where rolled back.

    When i examine the SQL Log, I see this:

    LogDate ProcessInfo Text

    ----------------------- ------------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    2015-06-05 11:55:44.680 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)

    Apr 2 2010 15:53:02

    Copyright (c) Microsoft Corporation

    Developer Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)

    2015-06-05 11:55:44.740 Server (c) Microsoft Corporation.

    2015-06-05 11:55:44.740 Server All rights reserved.

    2015-06-05 11:55:44.740 Server Server process ID is 2632.

    2015-06-05 11:55:44.740 Server Authentication mode is MIXED.

    2015-06-05 11:55:44.740 Server Logging SQL Server messages in file 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

    2015-06-05 11:55:44.740 Server This instance of SQL Server last reported using a process ID of 7948 at 05/06/2015 11:38:19 (local) 05/06/2015 14:38:19 (UTC). This is an informational message only; no user action is required.

    2015-06-05 11:55:44.740 Server Registry startup parameters:

    -d C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf

    -e C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG

    -l C:\Archivos de programa\Microso

    2015-06-05 11:55:44.790 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2015-06-05 11:55:44.790 Server Detected 4 CPUs. This is an informational message; no user action is required.

    2015-06-05 11:55:44.920 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.010 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.030 spid7s Starting up database 'master'.

    2015-06-05 11:55:45.130 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

    2015-06-05 11:55:45.250 spid7s Resource governor reconfiguration succeeded.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.260 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-06-05 11:55:45.280 spid7s SQL Trace ID 1 was started by login "sa".

    2015-06-05 11:55:45.300 spid7s The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe' instead of the curren

    2015-06-05 11:55:45.310 spid7s Starting up database 'mssqlsystemresource'.

    2015-06-05 11:55:45.340 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.510 spid7s Error: 15466, Severity: 16, State: 1.

    2015-06-05 11:55:45.510 spid7s An error occurred during decryption.

    2015-06-05 11:55:45.560 spid10s Starting up database 'model'.

    2015-06-05 11:55:45.560 spid7s Server name is 'DC'. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.560 spid7s Informational: No full-text supported languages found.

    2015-06-05 11:55:45.560 spid7s Starting up database 'msdb'.

    2015-06-05 11:55:45.760 spid10s Clearing tempdb database.

    2015-06-05 11:55:46.020 Server A self-generated certificate was successfully loaded for encryption.

    2015-06-05 11:55:46.020 Server Server is listening on [ 'any' <ipv4> 1433].

    2015-06-05 11:55:46.020 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

    2015-06-05 11:55:46.020 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].

    2015-06-05 11:55:46.020 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2015-06-05 11:55:46.020 Server Dedicated admin connection support was established for listening locally on port 1434.

    2015-06-05 11:55:46.040 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This i

    2015-06-05 11:55:46.040 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2015-06-05 11:55:46.060 spid10s Starting up database 'tempdb'.

    2015-06-05 11:55:46.110 spid13s The Service Broker protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s The Database Mirroring protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s Service Broker manager has started.

    2015-06-05 11:55:46.110 spid7s Recovery is complete. This is an informational message only. No user action is required.

    All the log previous to 2015-06-05 11:55 are missing, even from the same day. I have no idea where to look for.

    Thank you again

  • ericpap (6/8/2015)


    First, Thank you very much Grant and Steve for your help, and trying to undestand my problem. Sorry for the rush, but this a serious problem for me and i need to find what cause this problem. I will try to describe the problem, step by step.

    I have 3 user databases running on SQL Server 2008 R2 standard over a Windows 2003 Server. I don't administrate the server itself. Only install SQL Server and attach the databases. I'm a software developer, and my sofware use this databases for data store.

    Everything was working fine, when surprisely at 12am a user tell me that the data he enters in the software that same date is gone.

    So I go to SQL Server and to my surprise see that the main table has only two records when it should have at least 100. I continued searching and see that all the changes I did to the database en the past month (fields added to tables, views i created, stored procedures, etc) are missing. It's like someone restore and old backup or i gigantic transaction with all the changes where rolled back.

    When i examine the SQL Log, I see this:

    LogDate ProcessInfo Text

    ----------------------- ------------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    2015-06-05 11:55:44.680 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)

    Apr 2 2010 15:53:02

    Copyright (c) Microsoft Corporation

    Developer Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)

    2015-06-05 11:55:44.740 Server (c) Microsoft Corporation.

    2015-06-05 11:55:44.740 Server All rights reserved.

    2015-06-05 11:55:44.740 Server Server process ID is 2632.

    2015-06-05 11:55:44.740 Server Authentication mode is MIXED.

    2015-06-05 11:55:44.740 Server Logging SQL Server messages in file 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

    2015-06-05 11:55:44.740 Server This instance of SQL Server last reported using a process ID of 7948 at 05/06/2015 11:38:19 (local) 05/06/2015 14:38:19 (UTC). This is an informational message only; no user action is required.

    2015-06-05 11:55:44.740 Server Registry startup parameters:

    -d C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf

    -e C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG

    -l C:\Archivos de programa\Microso

    2015-06-05 11:55:44.790 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2015-06-05 11:55:44.790 Server Detected 4 CPUs. This is an informational message; no user action is required.

    2015-06-05 11:55:44.920 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.010 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.030 spid7s Starting up database 'master'.

    2015-06-05 11:55:45.130 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

    2015-06-05 11:55:45.250 spid7s Resource governor reconfiguration succeeded.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.260 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-06-05 11:55:45.280 spid7s SQL Trace ID 1 was started by login "sa".

    2015-06-05 11:55:45.300 spid7s The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe' instead of the curren

    2015-06-05 11:55:45.310 spid7s Starting up database 'mssqlsystemresource'.

    2015-06-05 11:55:45.340 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.510 spid7s Error: 15466, Severity: 16, State: 1.

    2015-06-05 11:55:45.510 spid7s An error occurred during decryption.

    2015-06-05 11:55:45.560 spid10s Starting up database 'model'.

    2015-06-05 11:55:45.560 spid7s Server name is 'DC'. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.560 spid7s Informational: No full-text supported languages found.

    2015-06-05 11:55:45.560 spid7s Starting up database 'msdb'.

    2015-06-05 11:55:45.760 spid10s Clearing tempdb database.

    2015-06-05 11:55:46.020 Server A self-generated certificate was successfully loaded for encryption.

    2015-06-05 11:55:46.020 Server Server is listening on [ 'any' <ipv4> 1433].

    2015-06-05 11:55:46.020 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

    2015-06-05 11:55:46.020 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].

    2015-06-05 11:55:46.020 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2015-06-05 11:55:46.020 Server Dedicated admin connection support was established for listening locally on port 1434.

    2015-06-05 11:55:46.040 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This i

    2015-06-05 11:55:46.040 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2015-06-05 11:55:46.060 spid10s Starting up database 'tempdb'.

    2015-06-05 11:55:46.110 spid13s The Service Broker protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s The Database Mirroring protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s Service Broker manager has started.

    2015-06-05 11:55:46.110 spid7s Recovery is complete. This is an informational message only. No user action is required.

    All the log previous to 2015-06-05 11:55 are missing, even from the same day. I have no idea where to look for.

    Thank you again

    Quick question. Is this a physical server or a VM? Also, did you omit the starting up of your user database(s) in the log? I only see the system databases.

  • Is this running on a VM? Might someone have restored an entire image?


    And then again, I might be wrong ...
    David Webb

  • The log is just showing a start up. That's not really terribly helpful.

    It sounds like someone restored a database, or possibly the VM as was suggested. The fact that your server is accessible and the database is accessible and your tables are there, but empty, all implies that your hardware is probably fine. We're looking at some type of actions caused by people or software (or a combination).

    If you connect to your SQL Server instance with SQL Server Management Studio, we can look at older logs. If you navigate through the Object Explorer window (which is open, on the left, by default) to Management and then expand that. You'll see "SQL Server Logs". Expand that. You should see a series of log files. Check the dates on those. See when they were created. See if you can find one that is between the date & time when you lost the data. Looking through that log, you should be able to see if databases were restored. Or, if the dates are all in the past, maybe someone restored your server.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • Thanks for the advice, but no, the server is not a virtual machine. It's a phisical machine

  • Grant Fritchey (6/8/2015)


    The log is just showing a start up. That's not really terribly helpful.

    It sounds like someone restored a database, or possibly the VM as was suggested. The fact that your server is accessible and the database is accessible and your tables are there, but empty, all implies that your hardware is probably fine. We're looking at some type of actions caused by people or software (or a combination).

    If you connect to your SQL Server instance with SQL Server Management Studio, we can look at older logs. If you navigate through the Object Explorer window (which is open, on the left, by default) to Management and then expand that. You'll see "SQL Server Logs". Expand that. You should see a series of log files. Check the dates on those. See when they were created. See if you can find one that is between the date & time when you lost the data. Looking through that log, you should be able to see if databases were restored. Or, if the dates are all in the past, maybe someone restored your server.

    Thanks for the advice. I already check for SQL Logs. Any log prior to the problem is lost. There is only two logs: an empty one, and the active one that start 06/05/2015 at 11:55, even when i know that the server and sql server was running before that this date and the previous ones.

  • Lynn Pettis (6/8/2015)


    ericpap (6/8/2015)


    First, Thank you very much Grant and Steve for your help, and trying to undestand my problem. Sorry for the rush, but this a serious problem for me and i need to find what cause this problem. I will try to describe the problem, step by step.

    I have 3 user databases running on SQL Server 2008 R2 standard over a Windows 2003 Server. I don't administrate the server itself. Only install SQL Server and attach the databases. I'm a software developer, and my sofware use this databases for data store.

    Everything was working fine, when surprisely at 12am a user tell me that the data he enters in the software that same date is gone.

    So I go to SQL Server and to my surprise see that the main table has only two records when it should have at least 100. I continued searching and see that all the changes I did to the database en the past month (fields added to tables, views i created, stored procedures, etc) are missing. It's like someone restore and old backup or i gigantic transaction with all the changes where rolled back.

    When i examine the SQL Log, I see this:

    LogDate ProcessInfo Text

    ----------------------- ------------ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    2015-06-05 11:55:44.680 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86)

    Apr 2 2010 15:53:02

    Copyright (c) Microsoft Corporation

    Developer Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)

    2015-06-05 11:55:44.740 Server (c) Microsoft Corporation.

    2015-06-05 11:55:44.740 Server All rights reserved.

    2015-06-05 11:55:44.740 Server Server process ID is 2632.

    2015-06-05 11:55:44.740 Server Authentication mode is MIXED.

    2015-06-05 11:55:44.740 Server Logging SQL Server messages in file 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

    2015-06-05 11:55:44.740 Server This instance of SQL Server last reported using a process ID of 7948 at 05/06/2015 11:38:19 (local) 05/06/2015 14:38:19 (UTC). This is an informational message only; no user action is required.

    2015-06-05 11:55:44.740 Server Registry startup parameters:

    -d C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf

    -e C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG

    -l C:\Archivos de programa\Microso

    2015-06-05 11:55:44.790 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2015-06-05 11:55:44.790 Server Detected 4 CPUs. This is an informational message; no user action is required.

    2015-06-05 11:55:44.920 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.010 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.030 spid7s Starting up database 'master'.

    2015-06-05 11:55:45.130 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

    2015-06-05 11:55:45.250 spid7s Resource governor reconfiguration succeeded.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.250 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

    2015-06-05 11:55:45.260 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

    2015-06-05 11:55:45.280 spid7s SQL Trace ID 1 was started by login "sa".

    2015-06-05 11:55:45.300 spid7s The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe' instead of the curren

    2015-06-05 11:55:45.310 spid7s Starting up database 'mssqlsystemresource'.

    2015-06-05 11:55:45.340 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.510 spid7s Error: 15466, Severity: 16, State: 1.

    2015-06-05 11:55:45.510 spid7s An error occurred during decryption.

    2015-06-05 11:55:45.560 spid10s Starting up database 'model'.

    2015-06-05 11:55:45.560 spid7s Server name is 'DC'. This is an informational message only. No user action is required.

    2015-06-05 11:55:45.560 spid7s Informational: No full-text supported languages found.

    2015-06-05 11:55:45.560 spid7s Starting up database 'msdb'.

    2015-06-05 11:55:45.760 spid10s Clearing tempdb database.

    2015-06-05 11:55:46.020 Server A self-generated certificate was successfully loaded for encryption.

    2015-06-05 11:55:46.020 Server Server is listening on [ 'any' <ipv4> 1433].

    2015-06-05 11:55:46.020 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

    2015-06-05 11:55:46.020 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].

    2015-06-05 11:55:46.020 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].

    2015-06-05 11:55:46.020 Server Dedicated admin connection support was established for listening locally on port 1434.

    2015-06-05 11:55:46.040 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This i

    2015-06-05 11:55:46.040 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2015-06-05 11:55:46.060 spid10s Starting up database 'tempdb'.

    2015-06-05 11:55:46.110 spid13s The Service Broker protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s The Database Mirroring protocol transport is disabled or not configured.

    2015-06-05 11:55:46.110 spid13s Service Broker manager has started.

    2015-06-05 11:55:46.110 spid7s Recovery is complete. This is an informational message only. No user action is required.

    All the log previous to 2015-06-05 11:55 are missing, even from the same day. I have no idea where to look for.

    Thank you again

    Quick question. Is this a physical server or a VM? Also, did you omit the starting up of your user database(s) in the log? I only see the system databases.

    Thanks. Yes User databases where started a few seconds later. The server is not a virtual machine

  • Is the storage for the server where the databases are hosted direct-attached storage or LUNs from a SAN? I have seen it where SAN failovers occurred but SAN replication failed causing the DB server to come online but the data being old (and quite possibly inconsistent).

    Joie Andrew
    "Since 1982"

  • there isn't a restore that has taken place, so either there's some storage change (possibly a restore of some sort) or a machine level change if you don't see anything in the current or last error log.

    SQL Server does not roll back changes from any corruption or other issue. It can only move forward, including moving forward from restores.

  • Steve Jones - SSC Editor (6/8/2015)


    there isn't a restore that has taken place, so either there's some storage change (possibly a restore of some sort) or a machine level change if you don't see anything in the current or last error log.

    SQL Server does not roll back changes from any corruption or other issue. It can only move forward, including moving forward from restores.

    The restore could have taken place in the part of the log that's missing.



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Have you looked at the event logs for the server?



    Alvin Ramard
    Memphis PASS Chapter[/url]

    All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

    For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Steve Jones - SSC Editor (6/8/2015)


    there isn't a restore that has taken place, so either there's some storage change (possibly a restore of some sort) or a machine level change if you don't see anything in the current or last error log.

    SQL Server does not roll back changes from any corruption or other issue. It can only move forward, including moving forward from restores.

    In that part of the log, but we clearly don't have everything. I'm pretty sure we're looking at a valid, if unfortunate, activity, probably a restore operation. I'm only saying that because the database is changed, not marked as suspect.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

Viewing 15 posts - 1 through 15 (of 67 total)

You must be logged in to reply to this topic. Login to reply