sqlbuddy123 (3/26/2014)
Check the Windows Application and System logs in the Event Veiwer ( Control Panel --> Administrative Tools ).--
SQLBuddy
From this query below I found create date of tempdb - last restart service - 2014-03-21 18:09:43.863
SELECT create_date FROM sys.databases WHERE name = 'tempdb'
Event Viewer I checked also
this is from Application
21. 3. 2014 18:07:21 Log was backed up. Database: DBNAME, creation date(time): 2014/01/03(18:23:26), first LSN: 48073:10596:1, last LSN: 48079:25339:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'TDPSQL-00000C78-0000'}). This is an informational message only. No user action is required.
21. 3. 2014 18:07:43 SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\USERDB\MCS_MESDB_1.ldf] in database [MCS_MESDB] (8). The OS file handle is 0x0000000000000D08. The offset of the latest long I/O is: 0x000002e70cb000
21. 3. 2014 18:08:31 SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3192. Thread=10908. Client. Instance=. VD=Global\TDPSQL-00000C78-0000_SQLVDIMemoryName_0.
21. 3. 2014 18:08:41 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
And Now I am seeing that I forgot System log, but time is after the problem, but maybe was problem with failoverclustering and it caused restart service,,, is it possible?
21. 3. 2014 18:08:39 Cluster resource 'SQL Server' of type 'SQL Server' in clustered role 'SQL Server (MSSQLSERVER)' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
21. 3. 2014 18:08:54 Cluster resource 'MES-SQL-CL' of type 'SQL Server Availability Group' in clustered role 'MES-SQL-CL' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
21. 3. 2014 18:09:22 A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSSQLSERVER service.
21. 3. 2014 18:09:26 Reset to device, \Device\RaidPort2, was issued.
21. 3. 2014 18:09:26 Cluster resource 'MES-SQL-CL' of type 'SQL Server Availability Group' in clustered role 'MES-SQL-CL' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
21. 3. 2014 18:09:26 The Cluster service failed to bring clustered service or application 'MES-SQL-CL' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
21. 3. 2014 18:09:26 Clustered role 'MES-SQL-CL' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
21. 3. 2014 18:09:37 The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s).
21. 3. 2014 18:09:39 The SQL Server (MSSQLSERVER) service entered the running state.