SQL Server Instance Level Queries

Daniel AG by Daniel A G

Query 1

 

SQL and OS Version information for current instance (Version Info)


select@@servername AS[server name], @@version AS [sql server and os version info];


-- SQL Server 2016 RTM Branch Builds


-- Build                         Description            Release Date   

-- 13.0.200.172             CTP 2.0                 5/26/2015

-- 13.0.300.44               CTP 2.1                 6/14/2015

-- 13.0.407.1                 CTP 2.2                 7/28/2015

-- 13.0.500.53               CTP 2.3                 9/4/2015

-- 13.0.600.65               CTP 2.4                 9/30/2015

-- 13.0.700.242             CTP 3.0                 10/29/2015

-- 13.0.900.73               CTP 3.2                 12/12/2015

-- 13.0.1000.276           CTP 3.3                 1/27/2016

-- 13.0.1100.288            RC0                      3/2/2016

-- 13.0.1200.242            RC1                      3/18/2016

-- 13.0.1300.275            RC2                      3/28/2016

-- 13.0.1400.361            RC3                      4/11/2016

-- 13.0.1601.5                RTM                     6/1/2016 


Query 2

 

Get socket, physical core and logical core count from the SQL Server Error log.(Core Counts)


EXEC sys.Xp_readerrorlog 

  0, 

  1, 

  N'detected', 

  N'socket'; 


This query might take a few seconds if you have not recycled your error log recently.This can help you determine the exact core counts used by SQL Server and whether HT is enabled or not.It can also help you confirm your SQL Server licensing model.Be on the lookout for this message "using 20 logical processors based on SQL Server licensing" which means grandfathered Server/CAL licensing.This query will return no results if your error log has been recycled since the instance was last started.


Query 3

 

Get selected server properties(Server Properties)


 

SELECT Serverproperty('machinename')                AS[machinename], 

       Serverproperty('servername')                 AS[servername], 

       Serverproperty('instancename')               AS [instance], 

       Serverproperty('isclustered')                AS [isclustered], 

       Serverproperty('computernamephysicalnetbios')AS [computernamephysicalnetbios], 

       Serverproperty('edition')                    AS [edition], 

       Serverproperty('productlevel')               AS[productlevel], --what servicing branch (rtm/sp/cu) 

       Serverproperty('productupdatelevel')         AS[productupdatelevel], 

       -- within a servicing branch, what cu# is applied 

       Serverproperty('productversion')      AS[productversion], 

       Serverproperty('productmajorversion') AS[productmajorversion], 

       Serverproperty('productminorversion') AS [productminorversion], 

       Serverproperty('productbuild')        AS[productbuild], 

       Serverproperty('productbuildtype')    AS[productbuildtype], 

       -- is this a gdr or od hotfix (null if on a cu build) 

       Serverproperty('productupdatereference') AS [productupdatereference], 

       -- kb article number that is applicable for this build 

       Serverproperty('processid')                 AS [processid], 

       Serverproperty('collation')                 AS [collation], 

       Serverproperty('isfulltextinstalled')       AS[isfulltextinstalled], 

       Serverproperty('isintegratedsecurityonly')  AS[isintegratedsecurityonly], 

       Serverproperty('filestreamconfiguredlevel') AS[filestreamconfiguredlevel], 

       Serverproperty('ishadrenabled')             AS[ishadrenabled], 

       Serverproperty('hadrmanagerstatus')         AS[hadrmanagerstatus], 

       Serverproperty('isxtpsupported')            AS [isxtpsupported], 

       Serverproperty('instancedefaultdatapath')   AS[instancedefaultdatapath], 

       Serverproperty('instancedefaultlogpath')    AS[instancedefaultlogpath], 

       Serverproperty('ispolybaseinstalled')       AS[ispolybaseinstalled], 

       --new for sql server 2016 

       Serverproperty('isadvancedanalyticsinstalled')              AS [isrservicesinstalled],

       - new FOR sql server 2016 serverproperty('buildclrversion') AS [build clrversion];


This gives you a lot of useful information about your instance of SQL Server, such as the ProcessID for SQL Server and your collation.Note: Some columns will be NULL on older SQL Server builds.


Query 4

 

Get instance-level configuration values for instance(Configuration Values)


SELECT NAME,       value,
       
value_in_use,
       
minimum,
       
maximum,
       
[description],
       
is_dynamic,
       
is_advanced
FROM   sys.configurations WITH (nolock)
ORDER  BY NAME
OPTION (recompile);  


Settings:automatic soft-NUMA disabled (should be 0 in most cases),backup checksum default (should be 1),backup compression default (should be 1 in most cases),clr enabled (only enable if it is needed),cost threshold for parallelism (depends on your workload),lightweight pooling (should be zero),max degree of parallelism (depends on your workload and hardware),max server memory (MB) (set to an appropriate value, not the default),optimize for ad hoc workloads (should be 1),priority boost (should be zero),remote admin connections (should be 1).

 

New configuration options for SQL Server 2016: allow polybase export (Allow INSERT into a Hadoop external table),automatic soft-NUMA disabled (Automatic soft-NUMA is enabled by default),external scripts enabled (Allows execution of external scripts, for R Services),hadoop connectivity (Configure SQL Server to connect to external Hadoop or Microsoft Azure storage blob data sources through PolyBase),polybase network encryption (Configure SQL Server to encrypt control and data channels when using PolyBase),remote data archive (Allow the use of the REMOTE_DATA_ARCHIVE data access for Stretch databases).


Query 5


Returns a list of all global trace flags that are enabled(Global Trace Flags)


DBCC tracestatus(-1); 


If no global trace flags are enabled, no results will be returned.It is very useful to know what global trace flags are currently enabled as part of the diagnostic process.Common trace flags that should be enabled in most cases.TF 3226 - Supresses logging of successful database backup messages to the SQL Server Error Log.The behavior of TF 1117, 1118 are enabled for tempdb in SQL Server 2016 by default.The behavior of TF 2371 is enabled by default in SQL Server 2016.


Query 6


Returns status of instant file initialization(IFI Status)


EXEC sys.Xp_readerrorlog 

  0, 
  1
, 
  
n'database instant file initialization';


Query 7


SQL Server Process Address space info(Process Memory)(shows whether locked pages is enabled, among other things)


SELECT physical_memory_in_use_kb / 1024 AS [sql server memory usage (mb)], 

       large_page_allocations_kb, 
       
locked_page_allocations_kb, 
       
page_fault_count, 
       
memory_utilization_percentage, 
       
available_commit_limit_kb, 
       
process_physical_memory_low, 
       
process_virtual_memory_low 
FROM   sys.dm_os_process_memory WITH (nolock) 
OPTION (recompile); 


You want to see 0 for process_physical_memory_low.You want to see 0 for process_virtual_memory_low.This indicates that you are not under internal memory pressure.


Query 8


SQL Server Services information(SQL Server Services Info)


SELECT servicename, 

       process_id, 
       
startup_type_desc, 
       
status_desc, 
       
last_startup_time, 
       
service_account, 
       
is_clustered, 
       
cluster_nodename, 
       
[filename] 
FROM   sys.dm_server_services WITH (nolock) 
OPTION (recompile); 


Tells you the account being used for the SQL Server Service and the SQL Agent Service.Shows the process_id, when they were last started, and their current status.Shows whether you are running on a failover cluster instance.


Query 9


Get SQL Server Agent jobs and Category information(SQL Server Agent Jobs)


SELECT sj.NAME                   AS [jobname], 

       sj.[description]          AS [jobdescription], 
       
Suser_sname(sj.owner_sid) AS [jobowner], 
       
sj.date_created, 
       
sj.[enabled], 
       
sj.notify_email_operator_id, 
       
sj.notify_level_email, 
       
sc.NAME                   AS [categoryname], 
       
js.next_run_date, 
       
js.next_run_time 
FROM   msdb.dbo.sysjobs AS sj WITH (nolock) 
       
INNER JOIN msdb.dbo.syscategories AS sc WITH (nolock) 
               
ON sj.category_id = sc.category_id 
       
LEFT OUTER JOIN msdb.dbo.sysjobschedules AS js WITH (nolock) 
                    
ON sj.job_id = js.job_id 
ORDER  BY sj.NAME 
OPTION (recompile); 


Gives you some basic information about your SQL Server Agent jobs, who owns them and how they are configured.Look for Agent jobs that are not owned by sa,Look for jobs that have a notify_email_operator_id set to 0 (meaning no operator).Look for jobs that have a notify_level_email set to 0 (meaning no e-mail is ever sent).


Query 10

 

Get SQL Server Agent Alert Information(SQL Server Agent Alerts)


SELECT NAME, 

       event_source, 
       
message_id, 
       
severity, 
       
[enabled], 
       
has_notification, 
       
delay_between_responses, 
       
occurrence_count, 
       
last_occurrence_date, 
       
last_occurrence_time 
FROM   msdb.dbo.sysalerts WITH (nolock) 
ORDER  BY NAME 
OPTION (recompile); 


Gives you some basic information about your SQL Server Agent Alerts (which are different from SQL Server Agent jobs).


Query 11

 

Windows information(Windows Info)


SELECT windows_release, 

       windows_service_pack_level, 
       
windows_sku, 
       
os_language_version 
FROM   sys.dm_os_windows_info WITH (nolock) 
OPTION (recompile); 


Gives you major OS version, Service Pack, Edition, and language info for the operating system,6.3 is either Windows 8.1, Windows 10 or Windows Server 2012 R2, Windows Server 2016,6.2 is either Windows 8 or Windows Server 2012,6.1 is either Windows 7 or Windows Server 2008 R2,6.0 is either Windows Vista or Windows Server 2008.

 

Windows SKU codes: 4 is Enterprise Edition,7 is Standard Server Edition,8 is Datacenter Server Edition,10 is Enterprise Server Edition,48 is Professional Edition,1033 for os_language_version is US-English.SQL Server 2014 requires Windows Server 2012 or newer.


Query 12

 

SQL Server NUMA Node information(SQL Server NUMA Info)


SELECT node_id, 

       node_state_desc, 
       
memory_node_id, 
       
processor_group, 
       
online_scheduler_count, 
       
active_worker_count, 
       
avg_load_balance, 
       
resource_monitor_state 
FROM   sys.dm_os_nodes WITH (nolock) 
WHERE  node_state_desc <> n'online dac' 
OPTION (recompile); 


Gives you some useful information about the composition and relative load on your NUMA nodes.You want to see an equal number of schedulers on each NUMA node.Watch out if SQL Server 2016 Standard Edition has been installed on a machine with more than 16 physical cores.


Query 13


Good basic information about OS memory amounts and state(System Memory)


SELECT total_physical_memory_kb / 1024     AS[Physical Memory (MB)], 

       available_physical_memory_kb / 1024 AS [Available Memory (MB)], 
       
total_page_file_kb / 1024           AS [Total Page File (MB)], 
       
available_page_file_kb / 1024       AS [Available Page File (MB)], 
       
system_cache_kb / 1024              AS [System Cache (MB)], 
       
system_memory_state_desc            AS [System Memory State] 
FROM   sys.dm_os_sys_memory WITH (nolock) 
OPTION (recompile); 


You want to see "Available physical memory is high" for System Memory State.This indicates that you are not under external memory pressure.You can skip the next three queries if you know you don't have a clustered instance.


Query 14

 

Shows you where the SQL Server failover cluster diagnostic log is located and how it is configured(SQL Server Error Log)


SELECT is_enabled, 

       [path], 
       
max_size, 
       
max_files 
FROM   sys.dm_os_server_diagnostics_log_configurations WITH (nolock) 
OPTION (recompile); 


Knowing this information is important for troubleshooting purposes.Also shows you the location of other error and diagnostic log files.


Query 15


Get information about your cluster nodes and their status(Cluster Node Properties)

(if your database server is in a failover cluster)


SELECT nodename, 

       status_description, 
       
is_current_owner 
FROM   sys.dm_os_cluster_nodes WITH (nolock) 
OPTION (recompile); 


Knowing which node owns the cluster resources is critical.Especially when you are installing Windows or SQL Server updates.You will see no results if your instance is not clustered.


Query 16

 

Get information about any AlwaysOn AG cluster this instance is a part of (Query 16)(AlwaysOn AG Cluster)


SELECT cluster_name, 

       quorum_type_desc, 
       
quorum_state_desc 
FROM   sys.dm_hadr_cluster WITH (nolock) 
OPTION (recompile);


You will see no results if your instance is not using AlwaysOn AGs.


Query 17

 

Hardware information from SQL Server 2016(Hardware Info)


SELECT cpu_count                     AS [logical cpu count], 

       scheduler_count, 
       
hyperthread_ratio             AS [hyperthread ratio], 
       
cpu_count / hyperthread_ratio AS [physical cpu count], 
       
physical_memory_kb / 1024     AS [physical memory (MB)], 
       
committed_kb / 1024           AS[committed memory (MB)], 
       
committed_target_kb / 1024    AS [committed target memory (MB)], 
       
max_workers_count             AS [max workers count], 
       
affinity_type_desc            AS [affinity type], 
       
sqlserver_start_time          AS [sql server start time], 
       
virtual_machine_type_desc     AS[virtual machine type], 
       
softnuma_configuration_desc   AS [soft numa configuration] 
FROM   sys.dm_os_sys_info WITH (nolock) 
OPTION (recompile); 


Gives you some good basic hardware information about your database server.Cannot distinguish between HT and multi-core. Note: virtual_machine_type_desc of HYPERVISOR does not automatically mean you are running SQL Server inside of a VM.It merely indicates that you have a hypervisor running on your host.Soft NUMA configuration is a new column for SQL Server 2016.


Query 18


Get System Manufacturer and model number from SQLServer Error log(System Manufacturer)


EXEC sys.Xp_readerrorlog 

  0, 
  1
, 
  
n'manufacturer'; 


This can help you determine the capabilities and capacities of your database server.Can also be used to confirm if you are running in a VM.This query might take a few seconds if you have not recycled your error l.


Query 19

 

Get processor description from Windows Registry(Processor Description)


EXEC sys.Xp_instance_regread 

  n'hkey_local_machine', 
  
n'hardware\description\system\centralprocessor\0', 
  
n'processornamestring'; 


Gives you the model number and rated clock speed of your processor(s).Your processors may be running at less than the rated clock speed due to the Windows Power Plan or hardware power management.


Query 20


See if buffer pool extension(BPE)is enabled(BPE Configuration)


SELECT [path], 

       state_description, 
       
current_size_in_kb, 
       
Cast (current_size_in_kb / 1048576.0 AS DECIMAL (10, 2)) AS [size (GB)] 
FROM   sys.dm_os_buffer_pool_extension_configuration WITH (nolock) 
OPTION (recompile); 


BPE is available in both Standard Edition and Enterprise Edition.It is a more interesting feature for Standard Edition.


Query 21

 

Look at buffer descriptors to see BPE usage by database(BPE Usage)


SELECT Db_name(database_id)                     AS [database name], 

       Count(page_id)                           AS [page count], 
       
Cast(Count(*) / 128.0 AS DECIMAL(10, 2)) AS [buffer size(mb)], 
       
Avg(read_microsec)                       AS 
       
[avg read time (microseconds)] 
FROM   sys.dm_os_buffer_descriptors WITH (nolock) 
WHERE  database_id <> 32767 
       
AND is_in_bpool_extension = 1 
GROUP  BY Db_name(database_id) 
ORDER  BY [buffer size(mb)] DESC 
OPTION (recompile); 


You will see no results if BPE is not enabled or if there is no BPE usage.


Query 22

 

Get information on location, time and size of any memory dumps from SQL Server (Memory Dump Info)


SELECT [filename], 

       creation_time, 
       
size_in_bytes / 1048576.0 AS [size (mb)] 
FROM   sys.dm_server_memory_dumps WITH (nolock) 
ORDER  BY creation_time DESC 
OPTION (recompile); 


This will not return any rows if you have.Not had any memory dumps (which is a good thing).

 

Query 23

 

File names and paths for all user and system databases on instance  (Database Filenames and Paths)


SELECT Db_name([database_id])          AS [database name], 

       [file_id], 
       
NAME, 
       
physical_name, 
       
[type_desc], 
       
state_desc, 
       
is_percent_growth, 
       
growth, 
       
CONVERT(BIGINT, growth / 128.0) AS [growth in mb], 
       
CONVERT(BIGINT, size / 128.0)   AS [total size in mb] 
FROM   sys.master_files WITH (nolock) 
ORDER  BY Db_name([database_id]) 
OPTION (recompile); 


Things to look at:Are data files and log files on different drives? Is everything on the C: drive?Is TempDB on dedicated drives?Is there only one TempDB data file? Are all of the TempDB data files the same size? Are there multiple data files for user databases?Is percent growth enabled for any files (which is bad)?


Query 24

 

Volume info for all LUNS that have database files on the current instance (Volume Info)


SELECT DISTINCT vs.volume_mount_point, 

                vs.file_system_type, 
                
vs.logical_volume_name, 
                
CONVERT(DECIMAL(18, 2), vs.total_bytes / 1073741824.0) 
                
AS [total size (gb)], 
                
CONVERT(DECIMAL(18, 2), vs.available_bytes / 1073741824.0) 
                
AS 
                
[available size (gb)], 
                
CONVERT(DECIMAL(18, 2), vs.available_bytes * 1. / vs.total_bytes 
                                        
* 100.) AS 
                
[space free %] 
FROM   sys.master_files AS f WITH (nolock) 
       
CROSS apply sys.Dm_os_volume_stats(f.database_id, f.[file_id]) AS vs 
ORDER  BY vs.volume_mount_point 
OPTION (recompile); 


Shows you the total and free space on the LUNs where you have database files. Being low on free space can negatively affect performance.


Query 25

 

Drive level latency information(Drive Level Latency)


SELECT tab.[drive], 

       tab.volume_mount_point AS [volume mount point], 
       
CASE 
         
WHEN num_of_reads = 0 THEN 0 
         
ELSE ( io_stall_read_ms / num_of_reads ) 
       
END                    AS [read latency], 
       
CASE 
         
WHEN num_of_writes = 0 THEN 0 
         
ELSE ( io_stall_write_ms / num_of_writes ) 
       
END                    AS [write latency], 
       
CASE 
         
WHEN ( num_of_reads = 0 
                
AND num_of_writes = 0 ) THEN 0 
         
ELSE ( io_stall / ( num_of_reads + num_of_writes ) ) 
       
END                    AS [overall latency], 
       
CASE 
         
WHEN num_of_reads = 0 THEN 0 
         
ELSE ( num_of_bytes_read / num_of_reads ) 
       
END                    AS [avg bytes/read], 
       
CASE 
         
WHEN num_of_writes = 0 THEN 0 
         
ELSE ( num_of_bytes_written / num_of_writes ) 
       
END                    AS [avg bytes/write], 
       
CASE 
         
WHEN ( num_of_reads = 0 
                
AND num_of_writes = 0 ) THEN 0 
         
ELSE ( ( num_of_bytes_read + num_of_bytes_written ) / 
                
( num_of_reads + num_of_writes ) ) 
       
END                    AS [avg bytes/transfer] 
FROM   (SELECT LEFT(Upper(mf.physical_name), 2) AS drive, 
               
Sum(num_of_reads)                AS num_of_reads, 
               
Sum(io_stall_read_ms)            AS io_stall_read_ms, 
               
Sum(num_of_writes)               AS num_of_writes, 
               
Sum(io_stall_write_ms)           AS io_stall_write_ms, 
               
Sum(num_of_bytes_read)           AS num_of_bytes_read, 
               
Sum(num_of_bytes_written)        AS num_of_bytes_written, 
               
Sum(io_stall)                    AS io_stall, 
               
vs.volume_mount_point 
        
FROM   sys.Dm_io_virtual_file_stats(NULL, NULL) AS vfs 
               
INNER JOIN sys.master_files AS mf WITH (nolock) 
                       
ON vfs.database_id = mf.database_id 
                          
AND vfs.file_id = mf.file_id 
               
CROSS apply sys.Dm_os_volume_stats(mf.database_id, mf.[file_id]) 
                           
AS vs 
        
GROUP  BY LEFT(Upper(mf.physical_name), 2), 
                  
vs.volume_mount_point) AS tab 
ORDER  BY [overall latency] 
OPTION (recompile); 


Shows you the drive-level latency for reads and writes, in milliseconds. Latency above 30-40ms is usually a problem.These latency numbers include all file activity against all SQL Server.Database file on each drive since SQL Server was last started.

 

Query 26

 

Calculates average stalls per read, per write, and per total input/output for each database file(IO Stalls by File)


SELECT Db_name(fs.database_id) 

       AS 
       
[database name], 
       
Cast(fs.io_stall_read_ms / ( 1.0 + fs.num_of_reads ) AS NUMERIC(10, 1)) 
       
AS 
       
[avg_read_stall_ms], 
       
Cast(fs.io_stall_write_ms / ( 1.0 + fs.num_of_writes ) AS NUMERIC(10, 1)) 
       
AS 
       
[avg_write_stall_ms], 
       
Cast(( fs.io_stall_read_ms + fs.io_stall_write_ms ) / ( 
                 1.0 
+ fs.num_of_reads + fs.num_of_writes ) AS NUMERIC(10, 1)) 
       
AS 
       
[avg_io_stall_ms], 
       
CONVERT(DECIMAL(18, 2), mf.size / 128.0) 
       
AS [file size (mb)], 
       
mf.physical_name, 
       
mf.type_desc, 
       
fs.io_stall_read_ms, 
       
fs.num_of_reads, 
       
fs.io_stall_write_ms, 
       
fs.num_of_writes, 
       
fs.io_stall_read_ms + fs.io_stall_write_ms 
       
AS [io_stalls], 
       
fs.num_of_reads + fs.num_of_writes 
       
AS [total_io], 
       
io_stall_queued_read_ms 
       
AS [resource governor total read io latency (ms)], 
       
io_stall_queued_write_ms 
       
AS [resource governor total write io latency (ms)] 
FROM   sys.Dm_io_virtual_file_stats(NULL, NULL) AS fs 
       
INNER JOIN sys.master_files AS mf WITH (nolock) 
               
ON fs.database_id = mf.database_id 
                  
AND fs.[file_id] = mf.[file_id] 
ORDER  BY avg_io_stall_ms DESC 
OPTION (recompile); 


Helps determine which database files on the entire instance have the most I/O bottlenecks.This can help you decide whether certain LUNs are overloaded and whether you might.Want to move some files to a different location or perhaps improve your I/O performance.These latency numbers include all file activity against each SQL Server.Database file since SQL Server was last started.

 

Query 27

 

Look for I/O requests taking longer than 15 seconds in the five most recent SQL Server Error Logs(IO Warnings)


CREATE TABLE #iowarningresults 

  ( 
     
logdate     DATETIME, 
     
processinfo SYSNAME, 
     
logtext     NVARCHAR(1000) 
  
); 

INSERT INTO #iowarningresults 
EXEC Xp_readerrorlog 
  0
, 
  1
, 
  
n'taking longer than 15 seconds'; 

INSERT INTO #iowarningresults 
EXEC Xp_readerrorlog 
  1
, 
  1
, 
  
n'taking longer than 15 seconds'; 

INSERT INTO #iowarningresults 
EXEC Xp_readerrorlog 
  2
, 
  1
, 
  
n'taking longer than 15 seconds'; 

INSERT INTO #iowarningresults 
EXEC Xp_readerrorlog 
  3
, 
  1
, 
  
n'taking longer than 15 seconds'; 

INSERT INTO #iowarningresults 
EXEC Xp_readerrorlog 
  4
, 
  1
, 
  
n'taking longer than 15 seconds'; 

SELECT logdate, 
       
processinfo, 
       
logtext 
FROM   #iowarningresults 
ORDER  BY logdate DESC; 

DROP TABLE #iowarningresults;


Finding 15 second I/O warnings in the SQL Server Error Log is useful evidence of:poor I/O performance (which might have many different causes).Look to see if you see any patterns in the results (same files, same drives, same time of day, etc.)

 

Query 28

 

Recovery model, log reuse wait description, log file size, log usage size  (Database Properties)and compatibility level for all databases on instance


SELECT db.[name]                                       AS [database name], 

       db.recovery_model_desc                          AS [recovery model], 
       
db.state_desc, 
       
db.containment_desc, 
       
db.log_reuse_wait_desc                          AS 
       
[log reuse wait description], 
       
CONVERT(DECIMAL(18, 2), ls.cntr_value / 1024.0) AS [log size (mb)], 
       
CONVERT(DECIMAL(18, 2), lu.cntr_value / 1024.0) AS [log used (mb)], 
       
Cast(Cast(lu.cntr_value AS FLOAT) / Cast(ls.cntr_value AS FLOAT)AS 
            DECIMAL
(18, 2)) * 100                      AS [log used %], 
       
db.[compatibility_level]                        AS 
       
[db compatibility level], 
       
db.is_mixed_page_allocation_on, 
       
db.page_verify_option_desc                      AS [page verify option], 
       
db.is_auto_create_stats_on, 
       
db.is_auto_update_stats_on, 
       
db.is_auto_update_stats_async_on, 
       
db.is_parameterization_forced, 
       
db.snapshot_isolation_state_desc, 
       
db.is_read_committed_snapshot_on, 
       
db.is_auto_close_on, 
       
db.is_auto_shrink_on, 
       
db.target_recovery_time_in_seconds, 
       
db.is_cdc_enabled, 
       
db.is_published, 
       
db.is_distributor, 
       
db.is_encrypted, 
       
db.group_database_id, 
       
db.replica_id, 
       
db.is_memory_optimized_elevate_to_snapshot_on, 
       
db.delayed_durability_desc, 
       
db.is_auto_create_stats_incremental_on, 
       
db.is_query_store_on, 
       
db.is_sync_with_backup, 
       
db.is_supplemental_logging_enabled, 
       
db.is_remote_data_archive_enabled, 
       
db.is_encrypted, 
       
de.encryption_state, 
       
de.percent_complete, 
       
de.key_algorithm, 
       
de.key_length 
FROM   sys.databases AS db WITH (nolock) 
       
INNER JOIN sys.dm_os_performance_counters AS lu WITH (nolock) 
               
ON db.NAME = lu.instance_name 
       
INNER JOIN sys.dm_os_performance_counters AS ls WITH (nolock) 
               
ON db.NAME = ls.instance_name 
       
LEFT OUTER JOIN sys.dm_database_encryption_keys AS de WITH (nolock) 
                    
ON db.database_id = de.database_id 
WHERE  lu.counter_name LIKE n'log file(s) used size (kb)%' 
       
AND ls.counter_name LIKE n'log file(s) size (kb)%' 
       
AND ls.cntr_value > 0 
OPTION (recompile); 


Things to look at: How many databases are on the instance?,What recovery models are they using?,What is the log reuse wait description?,How full are the transaction logs?, What compatibility level are the databases on?, What is the Page Verify Option? (should be CHECKSUM),Is Auto Update Statistics Asynchronously enabled?,Make sure auto_shrink and auto_close are not enabled!

 

Query 29

 

Missing Indexes for all databases by Index Advantage (Missing Indexes All Databases)


SELECT CONVERT(DECIMAL(18, 2), user_seeks * avg_total_user_cost * ( 

                                      avg_user_impact * 0.01 )) AS 
       
[index_advantage], 
       
migs.last_user_seek, 
       
mid.[statement]                                          AS 
       
[database.schema.table], 
       
mid.equality_columns, 
       
mid.inequality_columns, 
       
mid.included_columns, 
       
migs.unique_compiles, 
       
migs.user_seeks, 
       
migs.avg_total_user_cost, 
       
migs.avg_user_impact 
FROM   sys.dm_db_missing_index_group_stats AS migs WITH (nolock) 
       
INNER JOIN sys.dm_db_missing_index_groups AS mig WITH (nolock) 
               
ON migs.group_handle = mig.index_group_handle 
       
INNER JOIN sys.dm_db_missing_index_details AS mid WITH (nolock) 
               
ON mig.index_handle = mid.index_handle 
ORDER  BY index_advantage DESC 
OPTION (recompile); 


Getting missing index information for all of the databases on the instance is very useful.Look at last user seek time, number of user seeks to help determine source and importance.Also look at avg_user_impact and avg_total_user_cost to help determine importance.SQL Server is overly eager to add included columns, so beware.Do not just blindly add indexes that show up from this query!!!


Query 30

 

Get VLF Counts for all databases on the instance(VLF Counts) 


CREATE TABLE #vlfinfo 

  ( 
     
recoveryunitid INT, 
     
fileid         INT, 
     
filesize       BIGINT, 
     
startoffset    BIGINT, 
     
fseqno         BIGINT, 
     
[status]       BIGINT, 
     
parity         BIGINT, 
     
createlsn      NUMERIC(38) 
  
); 

CREATE TABLE #vlfcountresults 
  
( 
     
databasename SYSNAME, 
     
vlfcount     INT 
  
); 

EXEC Sp_msforeachdb 
n'use [?]; insert into #vlfinfo exec sp_executesql n''dbcc loginfo([?])'';                                                              insert into #vlfcountresults                                                              select db_name(), count(*) from #vlfinfo;                                                               truncate table #vlfinfo;' 

SELECT databasename, 
       
vlfcount 
FROM   #vlfcountresults 
ORDER  BY vlfcount DESC; 

DROP TABLE #vlfinfo; 
DROP TABLE #vlfcountresults; 


High VLF counts can affect write performance and they can make full database restores and crash recovery take much longer.Try to keep your VLF counts under 200 in most cases (depending on log file size).


Query 31

 

Get CPU utilization by database (CPU Usage by Database)


WITH db_cpu_stats 
     
AS (SELECT pa.databaseid, 
                
Db_name(pa.databaseid)           AS [database name], 
                
Sum(qs.total_worker_time / 1000) AS [cpu_time_ms] 
         
FROM   sys.dm_exec_query_stats AS qs WITH (nolock) 
                
CROSS apply (SELECT CONVERT(INT, value) AS [databaseid] 
                             
FROM   sys.Dm_exec_plan_attributes(qs.plan_handle) 
                             
WHERE  attribute = n'dbid') AS pa 
         
GROUP  BY databaseid) 
SELECT Row_number() 
         
OVER( 
           
ORDER BY [cpu_time_ms] DESC)                              AS 
       
[cpu rank], 
       
[database name], 
       
[cpu_time_ms]                                                 AS 
       
[cpu time (ms)], 
       
Cast([cpu_time_ms] * 1.0 / Sum([cpu_time_ms]) 
                                    
OVER() * 100.0 AS DECIMAL(5, 2)) AS 
       
[cpu percent] 
FROM   db_cpu_stats 
WHERE  databaseid <> 32767 -- resourcedb 
ORDER  BY [cpu rank] 
OPTION (recompile); 

Helps determine which database is using the most CPU resources on the instance.



Query 32


Get I/O utilization by database(IO Usage By Database)


WITH aggregate_io_statistics 

     AS (SELECT Db_name(database_id) AS [database name], 
                
Cast(Sum(num_of_bytes_read + num_of_bytes_written) / 1048576 AS 
                     DECIMAL
( 
                     12
, 2)) 
                                     
AS io_in_mb 
         
FROM   sys.Dm_io_virtual_file_stats(NULL, NULL) AS [dm_io_stats] 
         
GROUP  BY database_id) 
SELECT Row_number() 
         
OVER( 
           
ORDER BY io_in_mb DESC)                        AS [i/o rank], 
       
[database name], 
       
io_in_mb                                           AS [total i/o (mb)], 
       
Cast(io_in_mb / Sum(io_in_mb) 
                         
OVER() * 100.0 AS DECIMAL(5, 2)) AS [i/o percent] 
FROM   aggregate_io_statistics 
ORDER  BY [i/o rank] 
OPTION (recompile); 


Helps determine which database is using the most I/O resources on the instance.


Query 33


Get total buffer usage by database for current instance(Total Buffer Usage by Database).This make take some time to run on a busy instance.


WITH aggregatebufferpoolusage 

     AS (SELECT Db_name(database_id)                           AS 
                
[database name], 
                
Cast(Count(*) * 8 / 1024.0 AS DECIMAL (10, 2)) AS [cachedsize] 
         
FROM   sys.dm_os_buffer_descriptors WITH (nolock) 
         
WHERE  database_id <> 32767 -- resourcedb 
         
GROUP  BY Db_name(database_id)) 
SELECT Row_number() 
         
OVER( 
           
ORDER BY cachedsize DESC)                        AS 
       
[buffer pool rank], 
       
[database name], 
       
cachedsize                                           AS 
       
[cached size (mb)], 
       
Cast(cachedsize / Sum(cachedsize) 
                           
OVER() * 100.0 AS DECIMAL(5, 2)) AS 
       
[buffer pool percent] 
FROM   aggregatebufferpoolusage 
ORDER  BY [buffer pool rank] 
OPTION (recompile); 


Tells you how much memory (in the buffer pool).Is being used by each database on the instance.Clear Wait Stats with this command:


DBCC sqlperf('sys.dm_os_wait_stats', clear); 


Query 34


Isolate top waits for server instance since last restart or wait statistics clear(Top Waits)


WITH [waits] 

     AS (SELECT wait_type, 
                
wait_time_ms / 1000.0                           AS [waits], 
                
( wait_time_ms - signal_wait_time_ms ) / 1000.0 AS [resources], 
                
signal_wait_time_ms / 1000.0                    AS [signals], 
                
waiting_tasks_count                             AS [waitcount], 
                100.0 
* wait_time_ms / Sum (wait_time_ms) 
                                         
OVER()                 AS [percentage], 
                
Row_number() 
                  
OVER( 
                    
ORDER BY wait_time_ms DESC)                 AS [rownum] 
         
FROM   sys.dm_os_wait_stats WITH (nolock) 
         
WHERE  [wait_type] NOT IN ( 
                
n'broker_eventhandler', n'broker_receive_waitfor', 
                
n'broker_task_stop', 
                
n'broker_to_flush', 
                                     
n'broker_transmitter', n'checkpoint_queue', 
                
n'chkpt', 
                                           
n'clr_auto_event', 
                                     
n'clr_manual_event', n'clr_semaphore', 
                                           
n'dbmirror_dbm_event', 
                
n'dbmirror_events_queue' 
                
, 
                                     
n'dbmirror_worker_queue', 
                
n'dbmirroring_cmd', 
                                           
n'dirty_page_poll', 
                
n'dispatcher_queue_semaphore', 
                                     
n'execsync', n'fsagent', 
                
n'ft_ifts_scheduler_idle_wait', 
                                           
n'ft_iftshc_mutex', 
                                     
n'hadr_clusapi_call', 
                
n'hadr_filestream_iomgr_iocompletion' 
                                           
, 
                
n'hadr_logcapture_wait', 
                
n'hadr_notification_dequeue', 
                                     
n'hadr_timer_task', n'hadr_work_queue', 
                
n'ksource_wakeup', 
                                           
n'lazywriter_sleep' 
                                                                
, 
                                     
n'logmgr_queue', n'memory_allocation_ext', 
                                           
n'ondemand_task_queue', 
                
n'preemptive_os_libraryops', 
                                     
n'preemptive_os_comops', 
                
n'preemptive_os_cryptops', 
                                           
n'preemptive_os_pipeops', 
                                           
n'preemptive_os_authenticationops', 
                                     
n'preemptive_os_genericops', 
                
n'preemptive_os_verifytrust', 
                
n'preemptive_os_fileops' 
                
, 
                
n'preemptive_os_deviceops', 
                                     
n'pwait_all_components_initialized', 
                                           
n'qds_persist_task_main_loop_sleep', 
                
n'qds_async_queue', 
                
n'qds_cleanup_stale_queries_task_main_loop_sleep' 
                
, 
                                     
n'request_for_deadlock_search', 
                
n'resource_queue', 
                                           
n'server_idle_check', 
                                           
n'sleep_bpool_flush', 
                                     
n'sleep_dbstartup', n'sleep_dcomstartup', 
                                           
n'sleep_masterdbready', 
                                           
n'sleep_mastermdready', 
                                     
n'sleep_masterupgraded', 
                
n'sleep_msdbstartup', 
                                           
n'sleep_systemtask', 
                                           
n'sleep_task', 
                                     
n'sleep_tempdbstartup', n'sni_http_accept', 
                                           
n'sp_server_diagnostics_sleep', 
                                           
n'sqltrace_buffer_flush', 
                                     
n'sqltrace_incremental_flush_sleep', 
                                           
n'sqltrace_wait_entries', 
                                           
n'wait_for_results', n'waitfor', 
                                     
n'waitfor_taskshutdown', 
                
n'wait_xtp_host_wait', 
                                           
n'wait_xtp_offline_ckpt_new_log', 
                                           
n'wait_xtp_ckpt_close', 
                                     
n'xe_dispatcher_join', 
                
n'xe_dispatcher_wait', 
                                           
n'xe_live_target_tvf', 
                                           
n'xe_timer_event' ) 
                
AND waiting_tasks_count > 0) 
SELECT Max (w1.wait_type)                                                    AS 
       
[waittype], 
       
Cast (Max (w1.waits) AS DECIMAL (16, 2))                              AS 
       
[wait_sec], 
       
Cast (Max (w1.resources) AS DECIMAL (16, 2))                          AS 
       
[resource_sec], 
       
Cast (Max (w1.signals) AS DECIMAL (16, 2))                            AS 
       
[signal_sec], 
       
Max (w1.waitcount)                                                    AS 
       
[wait count], 
       
Cast (Max (w1.percentage) AS DECIMAL (5, 2))                          AS 
       
[wait percentage], 
       
Cast (( Max (w1.waits) / Max (w1.waitcount) ) AS DECIMAL (16, 4))     AS 
       
[avgwait_sec], 
       
Cast (( Max (w1.resources) / Max (w1.waitcount) ) AS DECIMAL (16, 4)) AS 
       
[avgres_sec], 
       
Cast (( Max (w1.signals) / Max (w1.waitcount) ) AS DECIMAL (16, 4))   AS 
       
[avgsig_sec] 
FROM   waits AS w1inner 
       
JOIN waits AS w2 
         
ON w2.rownum <= w1.rownum 
GROUP  BY w1.rownum 
HAVING Sum (w2.percentage) - Max (w1.percentage) < 99 -- percentage threshold 
OPTION (recompile); 


Cumulative wait stats are not as useful on an idle instance that is not under load or performance pressure.


Query 35


Get a count of SQL connections by IP address(Connection Counts by IP Address)


SELECT ec.client_net_address, 

       es.[program_name], 
       
es.[host_name], 
       
es.login_name, 
       
Count(ec.session_id) AS [connection count] 
FROM   sys.dm_exec_sessions AS es WITH (nolock) 
       
INNER JOIN sys.dm_exec_connections AS ec WITH (nolock) 
               
ON es.session_id = ec.session_id 
GROUP  BY ec.client_net_address, 
          
es.[program_name], 
          
es.[host_name], 
          
es.login_name 
ORDER  BY ec.client_net_address, 
          
es.[program_name] 
OPTION (recompile); 


This helps you figure where your database load is coming from and verifies connectivity from other machines.


Query 36


Get Average Task Counts (run multiple times)(Avg Task Counts)


SELECT Avg(current_tasks_count)   AS [avg task count], 

       Avg(work_queue_count)      AS [avg work queue count], 
       
Avg(runnable_tasks_count)  AS [avg runnable task count], 
       
Avg(pending_disk_io_count) AS [avg pending diskio count] 
FROM   sys.dm_os_schedulers WITH (nolock) 
WHERE  scheduler_id < 255 
OPTION (recompile); 


Sustained values above 10 suggest further investigation in that area.High Avg Task Counts are often caused by blocking/deadlocking or other resource contention.Sustained values above 1suggest further investigation in that area.High Avg Runnable Task Counts are a good sign of CPU pressure.High Avg Pending DiskIO Counts are a sign of disk pressure.


Query 37


Detect blocking (run multiple times)(Detect Blocking)


SELECT t1.resource_type                              AS [lock type], 

       Db_name(resource_database_id)                 AS [database], 
       
t1.resource_associated_entity_id              AS [blk object], 
       
t1.request_mode                               AS [lock req], 
       
--- lock requested 
       
t1.request_session_id                         AS [waiter sid], 
       
t2.wait_duration_ms                           AS [wait time], 
       
-- spid of waiter  
       
(SELECT [text] 
        
FROM   sys.dm_exec_requests AS r WITH (nolock) -- get sql for waiter 
               
CROSS apply sys.Dm_exec_sql_text(r.[sql_handle]) 
        
WHERE  r.session_id = t1.request_session_id) AS [waiter_batch], 
       
(SELECT Substring(qt.[text], r.statement_start_offset / 2, ( CASE 
                                                                      
WHEN 
               
r.statement_end_offset = -THEN Len( 
               
CONVERT(NVARCHAR(max), qt.[text])) 
                                                
* 
                                                2 
                                                                      
ELSE 
               
r.statement_end_offset 
                                                                    
END - 
               
r.statement_start_offset ) / 2) 
        
FROM   sys.dm_exec_requests AS r WITH (nolock) 
               
CROSS apply sys.Dm_exec_sql_text(r.[sql_handle]) AS qt 
        
WHERE  r.session_id = t1.request_session_id) AS [waiter_stmt], 
       
-- statement blocked 
       
t2.blocking_session_id                        AS [blocker sid], 
       
(SELECT [text] 
        
FROM   sys.sysprocesses AS p-- get sql for blocker 
               
CROSS apply sys.Dm_exec_sql_text(p.[sql_handle]) 
        
WHERE  p.spid = t2.blocking_session_id)      AS [blocker_batch] 
FROM   sys.dm_tran_locks AS t1 WITH (nolock) 
       
INNER JOIN sys.dm_os_waiting_tasks AS t2 WITH (nolock) 
               
ON t1.lock_owner_address = t2.resource_address 
OPTION (recompile); 

 


Helps troubleshoot blocking and deadlocking issues.The results will change from second to second on a busy system.You should run this query multiple times when you see signs of blocking.


Query 38


Get CPU Utilization History for last 256 minutesm (in one minute intervals) (CPU Utilization History)This version works with SQL Server 2016


DECLARE @ts_now BIGINT = (SELECT cpu_ticks / ( cpu_ticks / ms_ticks ) 

   FROM   sys.dm_os_sys_info WITH (nolock)); 

SELECT TOP(256) sqlprocessutilization                                  AS 
                
[sql server process cpu utilization], 
                
systemidle                                             AS 
                
[system idle process], 
                100 
- systemidle - sqlprocessutilization               AS 
                
[other process cpu utilization], 
                
Dateadd(ms, -* ( @ts_now - [timestamp] ), Getdate()) AS 
                
[event time] 
FROM   (SELECT record.value('(./record/@id)[1]', 'int') 
                      
AS record_id, 
record.value('(./record/schedulermonitorevent/systemhealth/systemidle)[1]', 'int')         AS
[systemidle], 
record.value('(./record/schedulermonitorevent/systemhealth/processutilization)[1]', 'int') AS [sqlprocessutilization], 
[timestamp] 
 
FROM   (SELECT [timestamp], 
                
CONVERT(XML, record) AS [record] 
         
FROM   sys.dm_os_ring_buffers WITH (nolock) 
         
WHERE  ring_buffer_type = n'ring_buffer_scheduler_monitor' 
                
AND record LIKE n'%<systemhealth>%') AS x) AS y 
ORDER  BY record_id DESC 
OPTION (recompile); 


Look at the trend over the entire period.Also look at high sustained Other Process CPU Utilization values.


Query 39


Get top total worker time queries for entire instance (Top Worker Time Queries)


SELECT TOP(50) 
            
Db_name(t.[dbid])                         AS [databasename], 
            
LEFT(t.[text], 50)                        AS [short query text], 
            
qs.total_worker_time                      AS [total worker time], 
            
qs.min_worker_time                        AS [min worker time], 
            
qs.total_worker_time/qs.execution_count   AS [avgworker time], 
            
qs.max_worker_time                        AS [max worker time], 
            
qs.min_elapsed_time                       AS [min elapsed time], 
            
qs.total_elapsed_time/qs.execution_count  AS [avg elapsed time], 
            
qs.max_elapsed_time                       AS [max elapsed time], 
            
qs.min_logical_reads                      AS [min logical reads], 
            
qs.total_logical_reads/qs.execution_count AS [avg logical reads], 
            
qs.max_logical_reads                      AS [max logical reads], 
            
qs.execution_count                        AS [execution count], 
            
qs.creation_time                          AS [creation time] 
            
-- ,t.[text] as [query text], qp.query_plan as 
            
[query plan] -- uncomment out these columns if not copying results to excel 
FROM        sys.dm_exec_query_stats             AS qs WITH (nolock) 
CROSS apply sys.dm_exec_sql_text(plan_handle)   AS t 
CROSS apply sys.dm_exec_query_plan(plan_handle) AS qp 
ORDER BY    qs.total_worker_time DESC OPTION(recompile);



Helps you find the most expensive queries from a CPU perspective across the entire instance.Can also help track down parameter sniffing issues.


Query 40

 

Page Life Expectancy (PLE) value for each NUMA node in current instance(PLE by NUMA Node)


SELECT @@servername AS [server name], 

       [object_name], 
       
instance_name, 
       
cntr_value   AS [page life expectancy] 
FROM   sys.dm_os_performance_counters WITH (nolock) 
WHERE  [object_name] LIKE n'%buffer node%' -- handles named instances 
       
AND counter_name = n'page life expectancy' 
OPTION (recompile); 


PLE is a good measurement of memory pressure.Higher PLE is better. Watch the trend over time, not the absolute value.This will only return one row for non-NUMA systems.

 

Query 41


Memory Grants Pending value for current instance(Memory Grants Pending)


SELECT @@servername AS [server name], 

       [object_name], 
       
cntr_value   AS [memory grants pending] 
FROM   sys.dm_os_performance_counters WITH (nolock) 
WHERE  [object_name] LIKE n'%memory manager%' -- handles named instances 
       
AND counter_name = n'memory grants pending' 
OPTION (recompile);


Run multiple times, and run periodically is you suspect you are under memory pressure.Memory Grants Pending above zero for a sustained period is a very strong indicator of internal memory pressure.


Query 42


Memory Clerk Usage for instance(Memory Clerk Usage).Look for high value for cachestore_sqlcp (ad-hoc query plans)


SELECT TOP(10) mc.[type]                                              AS 

               [memory clerk type], 
               
Cast(( Sum(mc.pages_kb) / 1024.0 ) AS DECIMAL (15, 2)) AS 
               
[memory usage (mb)] 
FROM   sys.dm_os_memory_clerks AS mc WITH (nolock) 
GROUP  BY mc.[type] 
ORDER  BY Sum(mc.pages_kb) DESC 
OPTION (recompile); 


MEMORYCLERK_SQLBUFFERPOOL was new for SQL Server 2012. It should be your highest consumer of memory. CACHESTORE_SQLCP  SQL Plans:These are cached SQL statements or batches that aren't in stored procedures, functions and triggers.Watch out for high values for CACHESTORE_SQLCP.CACHESTORE_OBJCP  Object Plans.These are compiled plans for stored procedures, functions and triggers.


Query 43

 

Find single-use, ad-hoc and prepared queries that are bloating the plan cache  (Ad hoc Queries)


SELECT TOP(50) [text]                  AS [querytext], 

               cp.cacheobjtype, 
               
cp.objtype, 
               
cp.size_in_bytes / 1024 AS [plan size in kb] 
FROM   sys.dm_exec_cached_plans AS cp WITH (nolock) 
       
CROSS apply sys.Dm_exec_sql_text(plan_handle) 
WHERE  cp.cacheobjtype = n'compiled plan' 
       
AND cp.objtype IN ( n'adhoc', n'prepared' ) 
       
AND cp.usecounts = 1 
ORDER  BY cp.size_in_bytes DESC 
OPTION (recompile); 


Gives you the text, type and size of single-use ad-hoc and prepared queries that waste space in the plan cache.Enabling 'optimize for ad hoc workloads' for the instance can help (SQL Server 2008 and above only).Running DBCC FREESYSTEMCACHE ('SQL Plans') periodically may be required to better control this.Enabling forced parameterization for the database can help, but test first!


Query 44


Get top total logical reads queries for entire instance (Top Logical Reads Queries)

 

SELECT TOP(50) Db_name(t.[dbid])                           AS [database name], 
               LEFT(t.[text], 50)                          AS [short query text] 
               , 
               qs.total_logical_reads                      AS 
               [total logical reads], 
               qs.min_logical_reads                        AS 
               [min logical reads], 
               qs.total_logical_reads / qs.execution_count AS 
               [avg logical reads], 
               qs.max_logical_reads                        AS 
               [max logical reads], 
               qs.min_worker_time                          AS [min worker time], 
               qs.total_worker_time / qs.execution_count   AS [avg worker time], 
               qs.max_worker_time                          AS [max worker time], 
               qs.min_elapsed_time                         AS [min elapsed time] 
               , 
               qs.total_elapsed_time / qs.execution_count  AS 
               [avg elapsed time], 
               qs.max_elapsed_time                         AS [max elapsed time] 
               , 
               qs.execution_count                          AS 
               [execution count], 
               qs.creation_time                            AS [creation time] 
-- ,t.[text] as [complete query text], qp.query_plan as [query plan] -- uncomment out these columns if not copying results to excel 
FROM   sys.dm_exec_query_stats AS qs WITH (nolock) 
       CROSS apply sys.Dm_exec_sql_text(plan_handle) AS t 
       CROSS apply sys.Dm_exec_query_plan(plan_handle) AS qp 
ORDER  BY qs.total_logical_reads DESC 
OPTION (recompile); 

Helps you find the most expensive queries from a memory perspective across the entire instance.Can also help track down parameter sniffing issues.




Statistics Says It All

16

Years of Experience

3000

Gratified Students

100

Training Batches

9600

Training Hours


Subscribe

Please subscribe our technical blog to get recent updates.

Empire Data Systems

Social Links