In this post, I am sharing few different scripts to find when was the SQL Server restarted.

The DBAs must know about this because they have to make sure about data consistency.

For example: when SQL Server restarted because of power failure, system failure, update failure or any other reason, We must check the last restarted time of SQL Server. Because from that time, we have to restore data from our backup disks to the actual disk.

When SQL Server restarted, few transactions also rollback. We have to also identify these transactions by knowing the correct time when SQL Server actually restarted.

Using sys.dm_exec_sessions:

SELECT login_time FROM sys.dm_exec_sessions WHERE session_id = 1
GO

Using sys.dm_os_sys_info:

SELECT sqlserver_start_time FROM sys.dm_os_sys_info
GO

Using sys.databases:

SELECT create_date FROM sys.databases WHERE name = 'tempdb' 
GO

Using sys.traces:

SELECT start_time FROM sys.traces WHERE is_default = 1  
GO

Using sysdatabases:

SELECT crdate FROM sysdatabases WHERE name='tempdb'  
GO

In this post, I am sharing a TSQL script to find the status of SQL Server Trace.

The SQL Server Trace is very important for tracing the different SQL Server events like errors, object changes information and others.

Using this script you can find different information of the Trace like Trace is running or not, Type of the trace, File path of the trace.

You can also visit this article to enable and disable SQL Server Default Trace.

I am fetching require trace column using an sys.traces.

Below is a script:

SELECT 
	CASE T.is_default
		WHEN 1 THEN 'Default/System Trace'
		WHEN 0 THEN 'User Defined Trace'
	END AS TraceType
	,CASE T.status
		WHEN 1 THEN 'Running'
		WHEN 0 THEN 'Stopped'
	END AS TraceStrace
	,ES.session_id AS SessionID
	,ES.login_name AS LoginName
	,T.Path AS TraceFilePath
FROM sys.traces AS T
LEFT JOIN sys.dm_exec_sessions AS ES
	ON T.reader_spid = ES.session_id