none
SQL SERVER 2012 日志文件丢失 RRS feed

  • 问题

  • 请问,我的数据库日志文件丢失了1个月的日志

    是什么原因导致数据库日志丢失?期间只做了重启的操作。

    2021年1月29日 6:21

全部回复

  • You mean DB transaction log (.ldf) or sql server error log?
    2021年1月30日 16:36
  • 丢失的具体表现是什么?数据少了一个月?仅日志(ldf)中少了?
    2021年2月1日 0:29
  • 日志丢失的同时,数据也同时丢失了一个月。

    日志是从ssms中导出来的。

    2021年2月1日 1:54
  • When the log is lost, the data is also lost for one month.
    Logs are exported from SSMS.
    2021年2月1日 1:55
  • 你好,

    >>日志是从ssms中导出来的。

    所以您说的是数据库的事务日志吗,导出来是指什么操作,备份?还是查询日志文件里的内容?

    日志丢失是指什么,是指数据库的事务日志文件(或内容)丢失,还是日志备份丢失。

    请详细说明一下您的问题,以便进一步的分析诊断。

    2021年2月1日 7:45
  • 数据库的日志文件和数据文件是分开的,日志数据的丢失不直接导致数据信息的丢失。
    2021年2月1日 9:06
  • 日志就是从ssms中的日志查看器看的。日志查看器记录丢失了1个月的日志,且同时间数据库数据也丢失了回退了1个月前版本
    2021年2月1日 13:57
  • When the log is lost, the data is also lost for one month.
    Logs are exported from SSMS.
    You still didn't say which log. Data lose maybe caused by mistake, can check db transaction log if db is not in simple recovery mode.
    2021年2月1日 17:14
  • 丢失的具体表现是什么?数据少了一个月?仅日志(ldf)中少了?
      那应该是被还原了吧?之前也遇到过一次,由于运维设置了错误的策略,导致虚拟机重启后还原到了错误的还原点
    • 已建议为答案 L.K.2584 2021年2月2日 10:15
    2021年2月2日 0:33
  • 重启服务器的操作期间,是否检查了数据库日志保存的完整性。
    2021年2月2日 1:12
  • 如何查看数据库还原到哪个还原点
    2021年2月2日 4:57

  • First ,one month of data loss in SQL SERVER LOG log。

    Second ,How to view the DB transaction log?


    2021年2月2日 5:05
  • The transaction log is viewed using DBCC, but the information inside is completely unknown. How to understand the information inside.
    2021年2月2日 5:22

  • First ,one month of data loss in SQL SERVER LOG log。

    Second ,How to view the DB transaction log?


    So you lost one month of info in sql server error log? Sql keeps 6 server error log files by default, sql will create new log file and delete oldest one every time you restarting sql server. That will not affect anything on the server. If you like to keep more sql server error log files, can change it in ssms.
    2021年2月2日 16:35
  • The transaction log is viewed using DBCC, but the information inside is completely unknown. How to understand the information inside.
    There's third party tool for that.
    2021年2月2日 16:35
  • 重启服务器的操作期间,是否检查了数据库日志保存的完整性。

    我的意思是整个系统被还原了,如果单纯只是数据库日志还原,SQL Server的日志是不受影响的

    你可以再检查一下操作系统日志,如果操作系统日志也丢失一个月,那么基本上可以确定是系统被还原了


    2021年2月3日 0:31
  • 我的理解是数据库系统正常运行期间,系统被重新启动,数据库日志未及时保存导致还原数据库时,数据丢失一个月。
    2021年2月3日 2:25
  • 重启服务器的操作期间,是否检查了数据库日志保存的完整性。

    我的意思是整个系统被还原了,如果单纯只是数据库日志还原,SQL Server的日志是不受影响的

    你可以再检查一下操作系统日志,如果操作系统日志也丢失一个月,那么基本上可以确定是系统被还原了


    系统操作日志没有丢失任何数据
    2021年2月3日 7:19
  • 把 SQL Server 最近的日志(含与丢失前接洽的那那部分)贴出来看看吧

    如果是数据库还原,不应该导致 SQL Server 自身的日志也丢失,所以应该是有更高一级的被还原行为

    2021年2月4日 0:36
  • 在当前数据库还原之前,若分离掉原数据库文件和日志文件,可以通过附加数据库操作恢复丢失的一个月数据。
    2021年2月4日 1:59
  • 把 SQL Server 最近的日志(含与丢失前接洽的那那部分)贴出来看看吧

    如果是数据库还原,不应该导致 SQL Server 自身的日志也丢失,所以应该是有更高一级的被还原行为

    日志文件如下,12月17日开始刀1月18日左右 期间少了一个月的日志。

    日期,源,严重性,消息
    
    
    
    01/18/2021 16:25:59,spid17s,未知,Starting up database 'WSS_Project_Doc'.
    01/18/2021 16:25:59,spid23s,未知,0 transactions rolled back in database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284' (10:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid23s,未知,167 transactions rolled forward in database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284' (10:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid17s,未知,0 transactions rolled back in database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a' (12:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid20s,未知,Starting up database 'StateService_b4dba4da7be04b62865bd9c6aa22476e'.
    01/18/2021 16:25:59,spid20s,未知,CHECKDB for database 'MMS' finished without errors on 2018-01-10 09:52:24.400 (local time). This is an informational message only; no user action is required.
    01/18/2021 16:25:59,spid21s,未知,Starting up database 'WSS_Company_Portal'.
    01/18/2021 16:25:59,spid19s,未知,Starting up database 'Search_Service_Application_LinksStoreDB_cb059c7bba984222be04ac2bc170d91e'.
    01/18/2021 16:25:59,spid17s,未知,13 transactions rolled forward in database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a' (12:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid25s,未知,Service Broker manager has started.
    01/18/2021 16:25:59,spid17s,未知,Starting up database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a'.
    01/18/2021 16:25:59,spid25s,未知,The Database Mirroring endpoint is in disabled or stopped state.
    01/18/2021 16:25:59,spid25s,未知,The Service Broker endpoint is in disabled or stopped state.
    01/18/2021 16:25:59,spid19s,未知,Recovery is writing a checkpoint in database 'SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814' (6). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid19s,未知,0 transactions rolled back in database 'SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814' (6:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:59,spid19s,未知,6 transactions rolled forward in database 'SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814' (6:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:58,spid6s,未知,Starting up database 'tempdb'.
    01/18/2021 16:25:58,spid21s,未知,Recovery is writing a checkpoint in database 'WSS_Logging' (8). This is an informational message only. No user action is required.
    01/18/2021 16:25:58,spid21s,未知,0 transactions rolled back in database 'WSS_Logging' (8:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:58,spid21s,未知,24 transactions rolled forward in database 'WSS_Logging' (8:0). This is an informational message only. No user action is required.
    01/18/2021 16:25:58,spid6s,未知,Clearing tempdb database.
    01/18/2021 16:25:58,spid6s,未知,Starting up database 'model'.
    01/18/2021 16:25:57,spid6s,未知,The resource database build version is 11.00.5058. This is an informational message only. No user action is required.
    01/18/2021 16:25:57,spid23s,未知,Starting up database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284'.
    01/18/2021 16:25:57,spid24s,未知,Starting up database 'Search_Service_Application_CrawlStoreDB_7f9f54bec56d4a8e895013d798b724da'.
    01/18/2021 16:25:57,spid22s,未知,Starting up database 'WSS_Communities'.
    01/18/2021 16:25:57,spid21s,未知,Starting up database 'WSS_Logging'.
    01/18/2021 16:25:57,spid20s,未知,Starting up database 'MMS'.
    01/18/2021 16:25:57,spid18s,未知,Starting up database 'SharePoint_Config'.
    01/18/2021 16:25:57,spid19s,未知,Starting up database 'SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814'.
    01/18/2021 16:25:57,spid17s,未知,Starting up database 'msdb'.
    01/18/2021 16:25:57,spid6s,未知,Starting up database 'mssqlsystemresource'.
    01/18/2021 16:25:57,spid14s,未知,A new instance of the full-text filter daemon host process has been successfully started.
    01/18/2021 16:25:56,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.108]
    01/18/2021 16:25:56,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    01/18/2021 16:25:56,Server,未知,Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    01/18/2021 16:25:55,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.107]
    01/18/2021 16:25:55,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    01/18/2021 16:25:55,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.107]
    01/18/2021 16:25:55,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    01/18/2021 16:25:55,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.107]
    01/18/2021 16:25:55,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    01/18/2021 16:25:54,Server,未知,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com:1433 ] for the SQL Server service.
    01/18/2021 16:25:54,Server,未知,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com ] for the SQL Server service.
    01/18/2021 16:25:54,Server,未知,SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    01/18/2021 16:25:54,spid13s,未知,SQL Server is now ready for client connections. This is an informational message; no user action is required.
    01/18/2021 16:25:54,spid13s,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\$$\SQLCLUSTERU02\sql\query ].
    01/18/2021 16:25:54,spid13s,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    01/18/2021 16:25:54,spid13s,未知,Started listening on virtual network name 'SQLCLUSTERU02'. No user action is required.
    01/18/2021 16:25:54,spid13s,未知,Server is listening on [ 10.70.38.136 <ipv4> 1433].
    01/18/2021 16:25:53,spid13s,未知,A self-generated certificate was successfully loaded for encryption.
    01/18/2021 16:25:53,spid5s,未知,The NETBIOS name of the local node that is running the server is 'SZHQSPSDBU02'. This is an informational message only. No user action is required.
    01/18/2021 16:25:53,spid5s,未知,Server name is 'SQLCLUSTERU02'. This is an informational message only. No user action is required.
    01/18/2021 16:25:53,spid5s,未知,SQL Trace ID 1 was started by login "sa".
    01/18/2021 16:25:52,spid5s,未知,SQL Server Audit has started the audits. This is an informational message. No user action is required.
    01/18/2021 16:25:52,spid5s,未知,SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    01/18/2021 16:25:52,spid5s,未知,CHECKDB for database 'master' finished without errors on 2019-07-11 14:04:28.593 (local time). This is an informational message only; no user action is required.
    01/18/2021 16:25:52,Server,未知,Software Usage Metrics is enabled.
    01/18/2021 16:25:52,Server,未知,CLR version v4.0.30319 loaded.
    01/18/2021 16:25:51,spid5s,未知,Starting up database 'master'.
    01/18/2021 16:25:51,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.
    01/18/2021 16:25:51,Server,未知,Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    01/18/2021 16:25:51,Server,未知,This instance of SQL Server last reported using a process ID of 4836 at 2021/1/18 16:19:53 (local) 2021/1/18 8:19:53 (UTC). This is an informational message only; no user action is required.
    01/18/2021 16:25:49,Server,未知,Using conventional memory in the memory manager.
    01/18/2021 16:25:49,Server,未知,Detected 8191 MB of RAM. This is an informational message; no user action is required.
    01/18/2021 16:25:49,Server,未知,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    01/18/2021 16:25:49,Server,未知,SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket<c/> 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    01/18/2021 16:25:47,Server,未知,Command Line Startup Parameters:<nl/>	 -s "MSSQLSERVER"
    01/18/2021 16:25:47,Server,未知,Registry startup parameters: <nl/>	 -d D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/>	 -e D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/>	 -l D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    01/18/2021 16:25:47,Server,未知,The service account is 'MTRSZU\sp_test_sql'. This is an informational message; no user action is required.
    01/18/2021 16:25:47,Server,未知,Logging SQL Server messages in file 'D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    01/18/2021 16:25:47,Server,未知,Authentication mode is MIXED.
    01/18/2021 16:25:47,Server,未知,System Manufacturer: 'VMware<c/> Inc.'<c/> System Model: 'VMware Virtual Platform'.
    01/18/2021 16:25:47,Server,未知,Server process ID is 4220.
    01/18/2021 16:25:47,Server,未知,All rights reserved.
    01/18/2021 16:25:47,Server,未知,(c) Microsoft Corporation.
    01/18/2021 16:25:46,Server,未知,Microsoft SQL Server 2012 - 11.0.5058.0 (X64) <nl/>	May 14 2014 18:34:29 <nl/>	Copyright (c) Microsoft Corporation<nl/>	Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    12/17/2020 20:51:33,spid14s,未知,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com:1433 ] for the SQL Server service.
    12/17/2020 20:51:33,spid14s,未知,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com ] for the SQL Server service.
    12/17/2020 20:51:33,spid5s,未知,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    12/17/2020 20:51:33,spid5s,未知,SQL Server shutdown has been initiated
    12/17/2020 20:51:32,spid5s,未知,.NET Framework runtime has been stopped.
    12/17/2020 20:51:32,spid26s,未知,Service Broker manager has shut down.
    12/17/2020 20:51:32,spid102,未知,The client was unable to reuse a session with SPID 102<c/> which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
    12/17/2020 20:51:32,spid102,未知,错误: 18056,严重性: 20,状态: 23。
    12/17/2020 20:51:32,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 在重新验证连接所使用的登录名时,服务器访问验证失败。 [客户端: 10.70.38.110]
    12/17/2020 20:51:32,Logon,未知,错误: 18456,严重性: 14,状态: 23。
    12/17/2020 20:51:32,spid78,未知,The client was unable to reuse a session with SPID 78<c/> which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
    12/17/2020 20:51:32,spid78,未知,错误: 18056,严重性: 20,状态: 23。
    12/17/2020 20:51:32,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 在重新验证连接所使用的登录名时,服务器访问验证失败。 [客户端: 10.70.38.110]
    12/17/2020 20:51:32,Logon,未知,错误: 18456,严重性: 14,状态: 23。
    12/17/2020 20:51:32,spid5s,未知,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
    12/17/2020 20:51:32,spid55,未知,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
    12/17/2020 20:50:11,spid212,未知,The transaction log for database 'Search_Service_Application_LinksStoreDB_cb059c7bba984222be04ac2bc170d91e' is full due to 'ACTIVE_TRANSACTION'.
    12/17/2020 20:50:11,spid212,未知,错误: 9002,严重性: 17,状态: 4。
    12/17/2020 20:47:31,spid5s,未知,Recovery is complete. This is an informational message only. No user action is required.
    12/17/2020 20:47:29,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Dept_Portal”。 [客户端: 10.70.38.108]
    12/17/2020 20:47:29,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:26,spid17s,未知,0 transactions rolled back in database 'MTRSZ_SP_Customization' (28:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:26,spid17s,未知,1 transactions rolled forward in database 'MTRSZ_SP_Customization' (28:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:26,spid17s,未知,Starting up database 'MTRSZ_SP_Customization'.
    12/17/2020 20:47:26,spid21s,未知,0 transactions rolled back in database 'User Profile Service Application_SyncDB_5044df27e4824572812881a21da12cf6' (20:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:26,spid21s,未知,1 transactions rolled forward in database 'User Profile Service Application_SyncDB_5044df27e4824572812881a21da12cf6' (20:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:26,spid25s,未知,Starting up database 'WSS_Dept_Portal'.
    12/17/2020 20:47:26,spid20s,未知,Starting up database 'WSS_Project_Doc3'.
    12/17/2020 20:47:26,spid55,未知,Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    12/17/2020 20:47:25,spid55,未知,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid17s,未知,Starting up database 'WSS_OTHERS'.
    12/17/2020 20:47:25,spid55,未知,Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    12/17/2020 20:47:25,spid19s,未知,Starting up database 'WSS_Other_Doc'.
    12/17/2020 20:47:25,spid55,未知,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    12/17/2020 20:47:25,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.108]
    12/17/2020 20:47:25,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:25,spid17s,未知,0 transactions rolled back in database 'User Profile Service Application_SocialDB_617ee735c4314284b56e8c5ff3f6fbee' (21:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid19s,未知,Recovery is writing a checkpoint in database 'SharePoint_Config' (5). This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid19s,未知,0 transactions rolled back in database 'SharePoint_Config' (5:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid17s,未知,407 transactions rolled forward in database 'User Profile Service Application_SocialDB_617ee735c4314284b56e8c5ff3f6fbee' (21:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid55,未知,Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    12/17/2020 20:47:25,spid23s,未知,Starting up database 'WSS_Operation_Doc'.
    12/17/2020 20:47:25,spid22s,未知,Starting up database 'WSS_Content_WorkFlow'.
    12/17/2020 20:47:25,spid55,未知,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid17s,未知,Starting up database 'User Profile Service Application_SocialDB_617ee735c4314284b56e8c5ff3f6fbee'.
    12/17/2020 20:47:25,spid19s,未知,72 transactions rolled forward in database 'SharePoint_Config' (5:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:25,spid21s,未知,Starting up database 'User Profile Service Application_SyncDB_5044df27e4824572812881a21da12cf6'.
    12/17/2020 20:47:24,spid24s,未知,Starting up database 'User Profile Service Application_ProfileDB_6d434c870323457ebc14abd5fdf558f0'.
    12/17/2020 20:47:24,spid24s,未知,0 transactions rolled back in database 'AppMng_Service_DB_53d8ff2d76d54123bb837228e026a7a8' (17:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid24s,未知,1 transactions rolled forward in database 'AppMng_Service_DB_53d8ff2d76d54123bb837228e026a7a8' (17:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid22s,未知,Starting up database 'WSS_Content'.
    12/17/2020 20:47:24,spid24s,未知,Starting up database 'AppMng_Service_DB_53d8ff2d76d54123bb837228e026a7a8'.
    12/17/2020 20:47:24,spid22s,未知,0 transactions rolled back in database 'StateService_b4dba4da7be04b62865bd9c6aa22476e' (15:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid17s,未知,Starting up database 'WSS_Project_Doc'.
    12/17/2020 20:47:24,spid22s,未知,1 transactions rolled forward in database 'StateService_b4dba4da7be04b62865bd9c6aa22476e' (15:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid22s,未知,Starting up database 'StateService_b4dba4da7be04b62865bd9c6aa22476e'.
    12/17/2020 20:47:24,spid21s,未知,Starting up database 'WSS_Company_Portal'.
    12/17/2020 20:47:24,spid21s,未知,CHECKDB for database 'MMS' finished without errors on 2018-01-10 09:52:24.400 (local time). This is an informational message only; no user action is required.
    12/17/2020 20:47:24,spid20s,未知,Starting up database 'Search_Service_Application_LinksStoreDB_cb059c7bba984222be04ac2bc170d91e'.
    12/17/2020 20:47:24,spid17s,未知,0 transactions rolled back in database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a' (12:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid24s,未知,Recovery is writing a checkpoint in database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284' (10). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid24s,未知,0 transactions rolled back in database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284' (10:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid24s,未知,1 transactions rolled forward in database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284' (10:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid17s,未知,13 transactions rolled forward in database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a' (12:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:24,spid26s,未知,Service Broker manager has started.
    12/17/2020 20:47:24,spid26s,未知,The Database Mirroring endpoint is in disabled or stopped state.
    12/17/2020 20:47:24,spid26s,未知,The Service Broker endpoint is in disabled or stopped state.
    12/17/2020 20:47:24,spid17s,未知,Starting up database 'Search_Service_Application_AnalyticsReportingStoreDB_1643e88ab5cb4f539266728a5fadf92a'.
    12/17/2020 20:47:23,spid6s,未知,Starting up database 'tempdb'.
    12/17/2020 20:47:23,spid6s,未知,Clearing tempdb database.
    12/17/2020 20:47:23,spid17s,未知,Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    12/17/2020 20:47:23,spid17s,未知,0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:23,spid17s,未知,5 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:23,spid6s,未知,Starting up database 'model'.
    12/17/2020 20:47:23,spid6s,未知,The resource database build version is 11.00.5058. This is an informational message only. No user action is required.
    12/17/2020 20:47:22,spid24s,未知,Starting up database 'Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284'.
    12/17/2020 20:47:22,spid25s,未知,Starting up database 'Search_Service_Application_CrawlStoreDB_7f9f54bec56d4a8e895013d798b724da'.
    12/17/2020 20:47:22,spid22s,未知,Starting up database 'WSS_Logging'.
    12/17/2020 20:47:22,spid23s,未知,Starting up database 'WSS_Communities'.
    12/17/2020 20:47:22,spid6s,未知,Starting up database 'mssqlsystemresource'.
    12/17/2020 20:47:22,spid21s,未知,Starting up database 'MMS'.
    12/17/2020 20:47:22,spid20s,未知,Starting up database 'SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814'.
    12/17/2020 20:47:22,spid19s,未知,Starting up database 'SharePoint_Config'.
    12/17/2020 20:47:22,spid17s,未知,Starting up database 'msdb'.
    12/17/2020 20:47:22,spid15s,未知,A new instance of the full-text filter daemon host process has been successfully started.
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_CrawlStoreDB_7f9f54bec56d4a8e895013d798b724da”。 [客户端: 10.70.38.110]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.110]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.110]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.109]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_AdminContent_160b8143-ced1-4cba-842d-bdba1fd0a814”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Project_Doc”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Project_Doc3”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_OTHERS”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Other_Doc”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Operation_Doc”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Dept_Portal”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.109]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.109]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.109]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“mms”。 [客户端: 10.70.38.109]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Content_WorkFlow”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_spappsvc'. 原因: 无法打开明确指定的数据库“Search_Service_Application_DB_fd1dc3bd5d30415190b523ae7a5f3284”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Content”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:22,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Communities”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:22,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:21,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“WSS_Company_Portal”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:21,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:21,Logon,未知,Login failed for user 'MTRSZU\sp_test_farm'. 原因: 无法打开明确指定的数据库“SharePoint_Config”。 [客户端: 10.70.38.107]
    12/17/2020 20:47:21,Logon,未知,错误: 18456,严重性: 14,状态: 38。
    12/17/2020 20:47:21,Server,未知,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com:1433 ] for the SQL Server service.
    12/17/2020 20:47:21,Server,未知,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/SQLCLUSTERU02.mtrszu.com ] for the SQL Server service.
    12/17/2020 20:47:21,Server,未知,SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    12/17/2020 20:47:21,spid14s,未知,SQL Server is now ready for client connections. This is an informational message; no user action is required.
    12/17/2020 20:47:21,spid14s,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\$$\SQLCLUSTERU02\sql\query ].
    12/17/2020 20:47:21,spid14s,未知,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    12/17/2020 20:47:21,spid14s,未知,Started listening on virtual network name 'SQLCLUSTERU02'. No user action is required.
    12/17/2020 20:47:21,spid14s,未知,Server is listening on [ 10.70.38.136 <ipv4> 1433].
    12/17/2020 20:47:21,spid14s,未知,A self-generated certificate was successfully loaded for encryption.
    12/17/2020 20:47:21,spid5s,未知,The NETBIOS name of the local node that is running the server is 'SZHQSPSDBU02'. This is an informational message only. No user action is required.
    12/17/2020 20:47:21,spid5s,未知,Server name is 'SQLCLUSTERU02'. This is an informational message only. No user action is required.
    12/17/2020 20:47:21,spid5s,未知,SQL Trace ID 1 was started by login "sa".
    12/17/2020 20:47:21,Server,未知,Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    12/17/2020 20:47:21,spid5s,未知,SQL Server Audit has started the audits. This is an informational message. No user action is required.
    12/17/2020 20:47:21,spid5s,未知,SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    12/17/2020 20:47:21,spid5s,未知,CHECKDB for database 'master' finished without errors on 2019-07-11 14:04:28.593 (local time). This is an informational message only; no user action is required.
    12/17/2020 20:47:21,Server,未知,Software Usage Metrics is enabled.
    12/17/2020 20:47:20,Server,未知,CLR version v4.0.30319 loaded.
    12/17/2020 20:47:20,spid5s,未知,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    12/17/2020 20:47:20,spid5s,未知,0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:20,spid5s,未知,11 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    12/17/2020 20:47:20,spid5s,未知,Starting up database 'master'.
    12/17/2020 20:47:20,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.
    12/17/2020 20:47:20,Server,未知,Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    12/17/2020 20:47:20,Server,未知,This instance of SQL Server last reported using a process ID of 4616 at 2020/12/17 20:47:07 (local) 2020/12/17 12:47:07 (UTC). This is an informational message only; no user action is required.
    12/17/2020 20:47:19,Server,未知,Using conventional memory in the memory manager.
    12/17/2020 20:47:19,Server,未知,Detected 8191 MB of RAM. This is an informational message; no user action is required.
    12/17/2020 20:47:19,Server,未知,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    12/17/2020 20:47:19,Server,未知,SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket<c/> 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    12/17/2020 20:47:19,Server,未知,Command Line Startup Parameters:<nl/>	 -s "MSSQLSERVER"
    12/17/2020 20:47:19,Server,未知,Registry startup parameters: <nl/>	 -d D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/>	 -e D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/>	 -l D:\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    12/17/2020 20:47:19,Server,未知,The service account is 'MTRSZU\sp_test_sql'. This is an informational message; no user action is required.
    12/17/2020 20:47:19,Server,未知,Logging SQL Server messages in file 'D:\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    12/17/2020 20:47:19,Server,未知,Authentication mode is MIXED.
    12/17/2020 20:47:19,Server,未知,System Manufacturer: 'VMware<c/> Inc.'<c/> System Model: 'VMware Virtual Platform'.
    12/17/2020 20:47:19,Server,未知,Server process ID is 1352.
    12/17/2020 20:47:19,Server,未知,All rights reserved.
    12/17/2020 20:47:19,Server,未知,(c) Microsoft Corporation.
    12/17/2020 20:47:18,Server,未知,Microsoft SQL Server 2012 - 11.0.5058.0 (X64) <nl/>	May 14 2014 18:34:29 <nl/>	Copyright (c) Microsoft Corporation<nl/>	Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    

    2021年2月4日 6:22
  • 12月17日异常关闭,1月18日重新启动,期间没有日志是正常的。

    2021年2月4日 7:48
  • 关键12月17和1月18日期间 都是正常使用的
    2021年2月4日 9:14
  • 从日志上看,你的 SQL Server运行在 VMWARE 虚拟机中,检查一下你的虚拟机设置或日志,严重怀疑是虚拟机还原了

    在网上找到一个关于VMWARE自动还原的设置,有这样的描述:

    勾选了“独立”,若再勾选“非永久”,则虚拟机关机后再重启,虚拟机将回到设定“非永久”时刻的状态(但虚拟机正常菜单下点击重启,原来的更改还存在!);

    2021年2月5日 0:57
  • 12月17和1月18日的系统日志贴出来看看吧。
    2021年2月5日 8:07
  • 关键12月17和1月18日期间 都是正常使用的
    Did VM team move your sql server around in that period?
    2021年2月5日 17:10