none
数据库每天早上都出现宕机,重启服务才能解决 RRS feed

  • 问题

  • 今天的报错日志如图(没有验证不让发图),每天都在这个时间出现此问题,请问各位大神,是什么停止了服务?如何查找?

    日期  2015/6/16 8:05:27
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [131] 由于用户、进程或操作系统的停止请求,SQLSERVERAGENT 服务正在停止...

    日期  2015/6/16 8:05:57
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [240] 1 个引擎线程未能在等待 30 秒后停止

    日期  2015/6/16 8:05:57
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [311] 线程“JobInvocationEngine”(ID 6868)仍在运行

    日期  2015/6/16 8:05:58
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [298] SQLServer 错误:  258,TCP 提供程序: 超时错误 [258]. [SQLSTATE 08001]

    日期  2015/6/16 8:05:58
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [165] ODBC 错误: 0,登录超时已过期 [SQLSTATE HYT00]

    日期  2015/6/16 8:05:58
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [298] SQLServer 错误:  258,由于预登录响应中的延迟,无法完成登录过程 [SQLSTATE 08001]

    日期  2015/6/16 8:05:58
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    日期  2015/6/16 8:06:02
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [382] 无法登录到服务器“(local)”(DisableAgentXPs)

    日期  2015/6/16 8:06:02
    日志  SQL Server 代理 (存档编号1 - 2015/6/16 8:06:00)

    消息
    [098] SQLServerAgent 已终止(强烈)

    数据库版本mssqlsever2008r2
    • 已编辑 TJ_Leo.s 2015年6月16日 5:54 补充
    2015年6月16日 5:47

全部回复

  • 请问楼主用的是什么程序,C#,JAVA,还是delphi?

    驱动程序用的是什么.net provider ? ODBC?

    网络是否良好,ping服务器是否有丢包?

    数据库有没有用什么特别的技术,例如数据库镜像?


    Love SQL

    2015年6月16日 10:30
  • Looks like someone stopped sql agent, any deatils in windows event logs?
    2015年6月16日 13:26
  • 从第一条日志信息来看,是有停止 sql server 的操作, 要看你的这个操作是正常的, 还是因为已经无法响应,导致你要去停止, 如果是前者,应该检查是什么原因有人会去停止, 如果是后者,你应该提供停止之前的日志
    2015年6月17日 1:33
  • 以前试过在sql2012上,用datasource从excel导入数据到sql,一执行那条sql,sqlserver服务马上停了


    Love SQL


    2015年6月17日 1:40
  • 程序是java,一个j2ee项目。

    用odbc连接

    网络是好的,因为这个时候我们可以远程登陆到问题服务器上,只是无法开启sql管理器,无法连接数据库

    数据库使用双机热备技术,但是此问题在主机和备机上一样会出现,我专门为此,特别观察了两天,挂在主机和备机上,数据库仍

    在早上7点40到8点30之间无法连接,sql错误日志反应的问题一样

    2015年6月17日 1:45
  • 由于问题只出现在早上的固定时段,而且那是用户最少的时候,所以不考虑是查询等操作照成了问题,每天此刻都会出现问题,但是计划任务在此时没有什么特别的动作
    2015年6月17日 1:48
  • 就看sql的错误日志,停止之前的错误日志,

    消息
    [131] 由于用户、进程或操作系统的停止请求,SQLSERVERAGENT 服务正在停止...

    这句是第一句。没有更早的错误日志

    每天这个时间也没有人为登陆数据库或者服务器做特别的动作

    2015年6月17日 1:51
  • 群集服务中的群集资源“SQL Server”或应用程序“SQL Server (MSSQLSERVER)”失败。

    这句是服务器log中在数据库异常是产生的记录

    2015年6月17日 1:55
  • 根据你说的

    群集服务中的群集资源“SQL Server”
    数据库使用双机热备技术

    你应该是使用了alwayson或者故障转移集群

    Love SQL

    2015年6月17日 2:01
  • 是的故障转移集群

    数据库使用的域账户

    由于前两周公司网络故障,一直不稳定

    我高度怀疑是域账户造成的问题

    但是又找不到确切证据和解决办法

    有办法么?

    2015年6月17日 2:14
  • 既然有网络不稳定的因素,考虑先把群集自动转移关闭吧, 看看是不是因为自动故障转移,导致 sql 服务停止的现象
    2015年6月17日 2:24
  • Check cluster log file, should have something if caused by failover.
    2015年6月17日 2:38
  • 你看大家都为你出谋划策,所以提问的时候一定要把情况说清楚


    Love SQL

    2015年6月17日 5:04
  • Current time is 08:23:59 06/20/15.                                                                              
    =====================================================================                                           
           BugCheck Dump                                                                                            
    =====================================================================                                           

    This file is generated by Microsoft SQL Server                                                                  
    version 10.50.1600.1                                                                                            
    upon detection of fatal unexpected error. Please return this file,                                              
    the query or program that produced the bugcheck, the database and                                               
    the error log, and any other pertinent information with a Service Request.                                      


    Computer type is Intel(R) Xeon(R) CPU           E7540  @ 2.00GHz.                                               
    Bios Version is HP     - 2                                                                                      
    48 X64 level 8664, 1 Mhz processor (s).                                                                         
    Windows NT 6.1 Build 7600 CSD .                                                                                 

    Memory                              
    MemoryLoad = 20%                    
    Total Physical = 32757 MB           
    Available Physical = 26086 MB       
    Total Page File = 65513 MB          
    Available Page File = 56118 MB      
    Total Virtual = 8388607 MB          
    Available Virtual = 8352864 MB      
    **Dump thread - spid = 0, EC = 0x0000000000000000                                                               
    ***Stack Dump being sent to F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0003.txt            
    * *******************************************************************************                               
    *                                                                                                               
    * BEGIN STACK DUMP:                                                                                             
    *   06/20/15 08:23:59 spid 7172                                                                                 
    *                                                                                                               
    * Deadlocked Schedulers                                                                                         
    *                                                                                                               
    * *******************************************************************************                               
    * -------------------------------------------------------------------------------                               
    * Short Stack Dump             

    以上是今早出的问题日志,此时负载很低,这是什么原因导致的?如何解决?

                                                                                                                                                                                                                                                                                                                                                                                                 
    • 已编辑 TJ_Leo.s 2015年6月20日 1:43
    2015年6月20日 1:39
  • 为了排除是网络或者域用户问题导致故障转移相关问题造成数据库异常,我已经把数据库放到新装的win2008R2系统的单机上,也是新装的sql2008r2,但是今早仍然出现了问题,请看我刚发的日志文件。请帮忙想想解决办法
    2015年6月20日 1:42
  • It's bug (scheduler deadlock), should install sp3 on the server.
    2015年6月20日 16:55
  • 看一下这个

    Reply from MS regarding the issue: This error message was recorded in the SQL Server error log when the deadlock scheduler dump was generated. This error happens when a deadlock occurs on the threads and all the threads are exhausted. For example, if an SPID started a transaction, but didn’t commit it, the transaction may get into the sleep status. And a lot of other SPID’s are waiting on that transaction to be committed. More and more requests were coming into the SQL Server, thus more and more threads were blocked by that transaction until all the threads were used up. When that transaction is ready to get committed, it found no more thread is available to do the job, and the deadlock happened.

    In this case, we found most of the threads were waiting for latch, and it was trying to generate the trace event and write that to the trace file. It was flushing the buffers for IO, and it’s waiting for the IO to complete. However it could be due to the IO delay, the flushing couldn’t finish in time. So we suggested  stopping the trace if possible and check the IO subsystem to make sure there is no bottleneck from there.

    帖子地址:https://social.technet.microsoft.com/Forums/sqlserver/en-US/1bb7516f-3d18-4e3d-9384-2e3dc1bcfb2e/hung-sql-server-deadlocked-scheduler?forum=sqldatabaseengine

    是不是您开了一个长事务,导致SQL已经无法处理了


    Love SQL

    2015年6月21日 1:20
  • 看一下这个

    Reply from MS regarding the issue: This error message was recorded in the SQL Server error log when the deadlock scheduler dump was generated. This error happens when a deadlock occurs on the threads and all the threads are exhausted. For example, if an SPID started a transaction, but didn’t commit it, the transaction may get into the sleep status. And a lot of other SPID’s are waiting on that transaction to be committed. More and more requests were coming into the SQL Server, thus more and more threads were blocked by that transaction until all the threads were used up. When that transaction is ready to get committed, it found no more thread is available to do the job, and the deadlock happened.

    In this case, we found most of the threads were waiting for latch, and it was trying to generate the trace event and write that to the trace file. It was flushing the buffers for IO, and it’s waiting for the IO to complete. However it could be due to the IO delay, the flushing couldn’t finish in time. So we suggested  stopping the trace if possible and check the IO subsystem to make sure there is no bottleneck from there.

    是不是您开了一个长事务,导致SQL已经无法处理了


    Love SQL


    那么我如何判断是否开了一个长事务?经过几天观察确认,每天8点24分,准时出现Short Stack Dump   ,这个和你说的长事务有可关系么?
    2015年6月21日 1:29
  • It's bug (scheduler deadlock), should install sp3 on the server.

    我刚刚按照你的建议,把sql2008r2的sp3在微软上找到了,现在已经装上,此Short Stack Dump   问题是sp3能解决的么?有这样的事例么?还是试试看?
    2015年6月21日 1:30
  • --查询数据库中的长事务

    SELECT  b.[session_id] , 
            b.[open_transaction_count],
    b.[total_elapsed_time],
            a.[name] AS 'transaction_name',
            b.[command] ,
            a.[transaction_begin_time] ,
            b.[blocking_session_id] ,
            DB_NAME(b.[database_id]) AS 'current_dbname'
    FROM    sys.[dm_tran_active_transactions] AS a
            INNER JOIN sys.[dm_exec_requests] AS b ON a.[transaction_id] = b.[transaction_id]
    WHERE [b].[database_id]=DB_ID()


    Love SQL

    2015年6月21日 1:34
  • --查询数据库中的长事务

    SELECT  b.[session_id] , 
            b.[open_transaction_count],
    b.[total_elapsed_time],
            a.[name] AS 'transaction_name',
            b.[command] ,
            a.[transaction_begin_time] ,
            b.[blocking_session_id] ,
            DB_NAME(b.[database_id]) AS 'current_dbname'
    FROM    sys.[dm_tran_active_transactions] AS a
            INNER JOIN sys.[dm_exec_requests] AS b ON a.[transaction_id] = b.[transaction_id]
    WHERE [b].[database_id]=DB_ID()


    Love SQL

    session_id open_transaction_count total_elapsed_time transaction_name command transaction_begin_time blocking_session_id current_dbname
    99 0 7 SELECT SELECT 2015-06-21 09:43:04.103 0 master

    结果集如上,是否正常?还需要做什么?

    2015年6月21日 1:44
  • DBCC INPUTBUFFER(spid)

    --将99代入进去,看一下具体sql是什么

    DBCC INPUTBUFFER(99)

    当然了,你现在那个长事务可能消失了,可能抓不出什么,最好在当时就运行这个语句


    Love SQL

    2015年6月21日 1:50
  • DBCC INPUTBUFFER(spid)

    --将99代入进去,看一下具体sql是什么

    DBCC INPUTBUFFER(99)

    当然了,你现在那个长事务可能消失了,可能抓不出什么,最好在当时就运行这个语句


    Love SQL

    EventType Parameters EventInfo
    Language Event 0   DBCC INPUTBUFFER(99)

    以上是结果集,看起来,经过--查询数据库中的长事务跑出的结果集是随着时间变化的,total_elapsed_time
    这个值每一秒都在0和8之间变化,经常返回的是0,感觉这个方法还是不能解释为什么每天8点24分就会出错。请问还有什么办法发现问题么?

    2015年6月21日 2:02
  • 我已经说了

    当然了,你现在那个长事务可能消失了,可能抓不出什么,最好在当时就运行这个语句

    或者您写个作业,每分钟执行一次,把抓到的内容和sql记录到一个表里面,这样不用自己经常手动执行了

    请参考

    http://www.cnblogs.com/lyhabc/p/4587811.html


    Love SQL

    2015年6月21日 2:07
  • 我已经说了

    当然了,你现在那个长事务可能消失了,可能抓不出什么,最好在当时就运行这个语句

    或者您写个作业,每分钟执行一次,把抓到的内容和sql记录到一个表里面,这样不用自己经常手动执行了

    请参考

    http://www.cnblogs.com/lyhabc/p/4587811.html


    Love SQL

    谢谢及时回答,在报错那一刻是无法运行此句子的,如果写入到作业定时执行,或许可以,可以试试,但是也只有在明天8点24以后才能抓出结果来,还有,由于此数据库为生产数据库,早上8点24那个时间并不是业务繁忙时段,也不能解释有定时执行了了一个长事务,不合理。

    2015年6月21日 2:17
  • It's bug (scheduler deadlock), should install sp3 on the server.


    我刚刚按照你的建议,把sql2008r2的sp3在微软上找到了,现在已经装上,此Short Stack Dump   问题是sp3能解决的么?有这样的事例么?还是试试看?
    That's what service pack and hotfix do, fixing bugs and adding new features.
    2015年6月21日 15:07
  • It's bug (scheduler deadlock), should install sp3 on the server.


    我刚刚按照你的建议,把sql2008r2的sp3在微软上找到了,现在已经装上,此Short Stack Dump   问题是sp3能解决的么?有这样的事例么?还是试试看?

    That's what service pack and hotfix do, fixing bugs and adding new features.

     SELECT @@VERSION

    Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)   Aug 19 2014 12:21:34   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    安装此包:SQLServer2008R2SP3-KB2979597-x64-CHS

    2015年6月22日 0:46
  • 问题解决了?

    Love SQL

    2015年6月22日 1:47
  • 问题解决了?

    Love SQL

    没有解决,问题依旧,今天早上出现了两次停止服务的问题,请看日志

    2015-06-22 08:11:03.83 Server      Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)
     Aug 19 2014 12:21:34
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    2015-06-22 08:11:03.83 Server      (c) Microsoft Corporation.
    2015-06-22 08:11:03.83 Server      All rights reserved.
    2015-06-22 08:11:03.83 Server      Server process ID is 9952.
    2015-06-22 08:11:03.83 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'ProLiant DL580 G7'.
    2015-06-22 08:11:03.83 Server      Authentication mode is MIXED.
    2015-06-22 08:11:03.83 Server      Logging SQL Server messages in file 'F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2015-06-22 08:11:03.83 Server      This instance of SQL Server last reported using a process ID of 1348 at 2015/6/22 7:55:32 (local) 2015/6/22 19:55:32 (UTC). This is an informational message only; no user action is required.
    2015-06-22 08:11:03.83 Server      Registry startup parameters:
      -d F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2015-06-22 08:11:03.85 服务器         SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-06-22 08:11:03.86 服务器         Detected 48 CPUs. This is an informational message; no user action is required.
    2015-06-22 08:11:04.04 服务器         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-22 08:11:04.04 服务器         Lock partitioning is enabled.  This is an informational message only. No user action is required.
    2015-06-22 08:11:04.09 服务器         Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000: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-22 08:11:04.09 服务器         Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff: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-22 08:11:04.09 服务器         Node configuration: node 2: CPU mask: 0x0000000fff000000:0 Active CPU mask: 0x0000000fff000000: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-22 08:11:04.09 服务器         Node configuration: node 3: CPU mask: 0x0000fff000000000:0 Active CPU mask: 0x0000fff000000000: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-22 08:11:04.14 spid11s     Starting up database 'master'.
    2015-06-22 08:11:04.21 spid11s     46 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.24 spid11s     0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.24 spid11s     Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.28 spid11s     CHECKDB for database 'master' finished without errors on 2015-06-21 08:59:24.223 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:04.29 spid11s     FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2015-06-22 08:11:04.33 spid11s     SQL Trace ID 1 was started by login "sa".
    2015-06-22 08:11:04.34 spid11s     Starting up database 'mssqlsystemresource'.
    2015-06-22 08:11:04.34 spid11s     The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
    2015-06-22 08:11:04.46 spid11s     Server name is 'NOD1'. This is an informational message only. No user action is required.
    2015-06-22 08:11:04.46 spid17s     Starting up database 'model'.
    2015-06-22 08:11:04.55 spid17s     Clearing tempdb database.
    2015-06-22 08:11:04.61 spid19s     A new instance of the full-text filter daemon host process has been successfully started.
    2015-06-22 08:11:04.64 spid19s     Starting up database 'msdb'.
    2015-06-22 08:11:04.64 spid20s     Starting up database 'PMPI'.
    2015-06-22 08:11:04.64 spid21s     Starting up database 'MonitorBlocking'.
    2015-06-22 08:11:04.68 spid19s     207 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.70 服务器         A self-generated certificate was successfully loaded for encryption.
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 'any' <ipv6> 1433].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 'any' <ipv4> 1433].
    2015-06-22 08:11:04.70 服务器         Server local connection provider is ready to accept connection on [ ].
    2015-06-22 08:11:04.70 服务器         Server local connection provider is ready to accept connection on [ ].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ ::1 <ipv6> 1434].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 127.0.0.1 <ipv4> 1434].
    2015-06-22 08:11:04.71 服务器         Dedicated admin connection support was established for listening locally on port 1434.
    2015-06-22 08:11:04.71 spid21s     20 transactions rolled forward in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.71 服务器         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 is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2015-06-22 08:11:04.71 spid19s     0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.71 服务器         SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2015-06-22 08:11:04.71 spid19s     Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.73 spid17s     Starting up database 'tempdb'.
    2015-06-22 08:11:04.75 spid21s     0 transactions rolled back in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.75 spid21s     Recovery is writing a checkpoint in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.75 spid22s     The Service Broker protocol transport is disabled or not configured.
    2015-06-22 08:11:04.75 spid22s     The Database Mirroring protocol transport is disabled or not configured.
    2015-06-22 08:11:04.76 spid22s     Service Broker manager has started.
    2015-06-22 08:11:04.81 spid21s     CHECKDB for database 'MonitorBlocking' finished without errors on 2015-06-20 09:26:32.090 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:05.15 spid20s     Recovery of database 'PMPI' (5) is 0% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
    2015-06-22 08:11:05.16 spid20s     Recovery of database 'PMPI' (5) is 0% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.84 spid20s     1046 transactions rolled forward in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.13 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.13 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.41 spid20s     0 transactions rolled back in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.41 spid20s     Recovery is writing a checkpoint in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:08.06 spid20s     Recovery completed for database PMPI (database ID 5) in 2 second(s) (analysis 31 ms, redo 1674 ms, undo 563 ms.) This is an informational message only. No user action is required.
    2015-06-22 08:11:08.10 spid20s     CHECKDB for database 'PMPI' finished without errors on 2012-04-26 00:00:02.750 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:08.13 spid11s     Recovery is complete. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.21 spid249     Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.21 spid249     Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2015-06-22 08:11:10.44 spid249     Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.44 spid249     Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2015-06-22 08:11:10.53 spid249     Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.54 spid249     Using 'xplog70.dll' version '2009.100.6000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2015-06-22 08:12:04.21 spid257     Process ID 172 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:12:04.21 spid257     Process ID 166 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.71 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:16:43.71 spid269     DBCC CHECKDB (master) executed by sa found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  内部  数据库快照的拆分点 LSN 为 000000c2:00000147:0002,第一个 LSN 为 000000c2:00000146:0001。
    2015-06-22 08:16:46.02 spid269     DBCC CHECKDB (mssqlsystemresource) executed by sa found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 2 seconds. 
    2015-06-22 08:24:34.26 Server      Using 'dbghelp.dll' version '4.0.5'
    2015-06-22 08:24:34.29 Server      **Dump thread - spid = 0, EC = 0x0000000000000000
    2015-06-22 08:24:34.29 Server      ***Stack Dump being sent to F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0005.txt
    2015-06-22 08:24:34.29 Server      * *******************************************************************************
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * BEGIN STACK DUMP:
    2015-06-22 08:24:34.29 Server      *   06/22/15 08:24:34 spid 10120
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * Deadlocked Schedulers
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * *******************************************************************************
    2015-06-22 08:24:34.29 Server      * -------------------------------------------------------------------------------
    2015-06-22 08:24:34.29 Server      * Short Stack Dump
    2015-06-22 08:24:34.35 Server      Stack Signature for the dump is 0x00000000000003AD

    2015年6月22日 1:54
  • 问题解决了?

    Love SQL

    问题没有解决,而且今天出现了两次停止服务,请看日志

    2015-06-22 08:11:03.83 Server      Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)
     Aug 19 2014 12:21:34
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

    2015-06-22 08:11:03.83 Server      (c) Microsoft Corporation.
    2015-06-22 08:11:03.83 Server      All rights reserved.
    2015-06-22 08:11:03.83 Server      Server process ID is 9952.
    2015-06-22 08:11:03.83 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'ProLiant DL580 G7'.
    2015-06-22 08:11:03.83 Server      Authentication mode is MIXED.
    2015-06-22 08:11:03.83 Server      Logging SQL Server messages in file 'F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2015-06-22 08:11:03.83 Server      This instance of SQL Server last reported using a process ID of 1348 at 2015/6/22 7:55:32 (local) 2015/6/22 19:55:32 (UTC). This is an informational message only; no user action is required.
    2015-06-22 08:11:03.83 Server      Registry startup parameters:
      -d F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2015-06-22 08:11:03.85 服务器         SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-06-22 08:11:03.86 服务器         Detected 48 CPUs. This is an informational message; no user action is required.
    2015-06-22 08:11:04.04 服务器         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-22 08:11:04.04 服务器         Lock partitioning is enabled.  This is an informational message only. No user action is required.
    2015-06-22 08:11:04.09 服务器         Node configuration: node 0: CPU mask: 0x0000000000fff000:0 Active CPU mask: 0x0000000000fff000: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-22 08:11:04.09 服务器         Node configuration: node 1: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff: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-22 08:11:04.09 服务器         Node configuration: node 2: CPU mask: 0x0000000fff000000:0 Active CPU mask: 0x0000000fff000000: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-22 08:11:04.09 服务器         Node configuration: node 3: CPU mask: 0x0000fff000000000:0 Active CPU mask: 0x0000fff000000000: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-22 08:11:04.14 spid11s     Starting up database 'master'.
    2015-06-22 08:11:04.21 spid11s     46 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.24 spid11s     0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.24 spid11s     Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.28 spid11s     CHECKDB for database 'master' finished without errors on 2015-06-21 08:59:24.223 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:04.29 spid11s     FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2015-06-22 08:11:04.33 spid11s     SQL Trace ID 1 was started by login "sa".
    2015-06-22 08:11:04.34 spid11s     Starting up database 'mssqlsystemresource'.
    2015-06-22 08:11:04.34 spid11s     The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
    2015-06-22 08:11:04.46 spid11s     Server name is 'NOD1'. This is an informational message only. No user action is required.
    2015-06-22 08:11:04.46 spid17s     Starting up database 'model'.
    2015-06-22 08:11:04.55 spid17s     Clearing tempdb database.
    2015-06-22 08:11:04.61 spid19s     A new instance of the full-text filter daemon host process has been successfully started.
    2015-06-22 08:11:04.64 spid19s     Starting up database 'msdb'.
    2015-06-22 08:11:04.64 spid20s     Starting up database 'PMPI'.
    2015-06-22 08:11:04.64 spid21s     Starting up database 'MonitorBlocking'.
    2015-06-22 08:11:04.68 spid19s     207 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.70 服务器         A self-generated certificate was successfully loaded for encryption.
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 'any' <ipv6> 1433].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 'any' <ipv4> 1433].
    2015-06-22 08:11:04.70 服务器         Server local connection provider is ready to accept connection on [  ].
    2015-06-22 08:11:04.70 服务器         Server local connection provider is ready to accept connection on [ ].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ ::1 <ipv6> 1434].
    2015-06-22 08:11:04.70 服务器         Server is listening on [ 127.0.0.1 <ipv4> 1434].
    2015-06-22 08:11:04.71 服务器         Dedicated admin connection support was established for listening locally on port 1434.
    2015-06-22 08:11:04.71 spid21s     20 transactions rolled forward in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.71 服务器         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 is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2015-06-22 08:11:04.71 spid19s     0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.71 服务器         SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2015-06-22 08:11:04.71 spid19s     Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.73 spid17s     Starting up database 'tempdb'.
    2015-06-22 08:11:04.75 spid21s     0 transactions rolled back in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.75 spid21s     Recovery is writing a checkpoint in database 'MonitorBlocking' (6). This is an informational message only. No user action is required.
    2015-06-22 08:11:04.75 spid22s     The Service Broker protocol transport is disabled or not configured.
    2015-06-22 08:11:04.75 spid22s     The Database Mirroring protocol transport is disabled or not configured.
    2015-06-22 08:11:04.76 spid22s     Service Broker manager has started.
    2015-06-22 08:11:04.81 spid21s     CHECKDB for database 'MonitorBlocking' finished without errors on 2015-06-20 09:26:32.090 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:05.15 spid20s     Recovery of database 'PMPI' (5) is 0% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
    2015-06-22 08:11:05.16 spid20s     Recovery of database 'PMPI' (5) is 0% complete (approximately 8 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.76 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:06.76 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:06.84 spid20s     1046 transactions rolled forward in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.13 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.13 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.17 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.17 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.18 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.18 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.19 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.19 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.20 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.20 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.21 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.21 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.41 spid20s     0 transactions rolled back in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.41 spid20s     Recovery is writing a checkpoint in database 'PMPI' (5). This is an informational message only. No user action is required.
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:07.56 登录          错误: 18456,严重性: 14,状态: 38。
    2015-06-22 08:11:07.56 登录          Login failed for user 'sa'. 原因: 无法打开明确指定的数据库。 [客户端: 172.16.7.14]
    2015-06-22 08:11:08.06 spid20s     Recovery completed for database PMPI (database ID 5) in 2 second(s) (analysis 31 ms, redo 1674 ms, undo 563 ms.) This is an informational message only. No user action is required.
    2015-06-22 08:11:08.10 spid20s     CHECKDB for database 'PMPI' finished without errors on 2012-04-26 00:00:02.750 (local time). This is an informational message only; no user action is required.
    2015-06-22 08:11:08.13 spid11s     Recovery is complete. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.21 spid249     Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.21 spid249     Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2015-06-22 08:11:10.44 spid249     Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.44 spid249     Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2015-06-22 08:11:10.53 spid249     Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    2015-06-22 08:11:10.54 spid249     Using 'xplog70.dll' version '2009.100.6000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2015-06-22 08:12:04.21 spid257     Process ID 172 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:12:04.21 spid257     Process ID 166 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.69 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.70 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:13:00.71 spid268     Process ID 257 was killed by hostname NOD1, host process ID 6232.
    2015-06-22 08:16:43.71 spid269     DBCC CHECKDB (master) executed by sa found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  内部  数据库快照的拆分点 LSN 为 000000c2:00000147:0002,第一个 LSN 为 000000c2:00000146:0001。
    2015-06-22 08:16:46.02 spid269     DBCC CHECKDB (mssqlsystemresource) executed by sa found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 2 seconds. 
    2015-06-22 08:24:34.26 Server      Using 'dbghelp.dll' version '4.0.5'
    2015-06-22 08:24:34.29 Server      **Dump thread - spid = 0, EC = 0x0000000000000000
    2015-06-22 08:24:34.29 Server      ***Stack Dump being sent to F:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0005.txt
    2015-06-22 08:24:34.29 Server      * *******************************************************************************
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * BEGIN STACK DUMP:
    2015-06-22 08:24:34.29 Server      *   06/22/15 08:24:34 spid 10120
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * Deadlocked Schedulers
    2015-06-22 08:24:34.29 Server      *
    2015-06-22 08:24:34.29 Server      * *******************************************************************************
    2015-06-22 08:24:34.29 Server      * -------------------------------------------------------------------------------
    2015-06-22 08:24:34.29 Server      * Short Stack Dump
    2015-06-22 08:24:34.35 Server      Stack Signature for the dump is 0x00000000000003AD

    从日志看,8点11一次,8点24一次,目前还是没有找到问题根源,已经装上SP3补丁,今天还是这样,还有什么办法?


    • 已编辑 TJ_Leo.s 2015年6月22日 2:01 修改
    2015年6月22日 1:56
  • 干嘛做DBCC CHECKDB??

    Love SQL

    2015年6月22日 2:01
  • 干嘛做DBCC CHECKDB??

    Love SQL


    在网上看,有人介绍我用此方法查找是否有错误。
    2015年6月22日 2:03
  • 应该和os日志一起看,尤其底层日志
    2015年7月8日 15:26