Performance Tuning with SQL Server Dynamic Management Views

Chapter 2: Connections, Sessions and Requests
would review the activity associated with the Transport View application to
determine whether or not multiple connections, and multiple sources of said
connections, are appropriate.
It is quite common that many, if not most, of the Application Servers in your
environment will be generating multiple connections into your SQL Server boxes.
However, if you observe the same behavior from a workstation, you may need to
investigate the usage patterns of the application with the application analyst or
vendor representative, to determine if this is an architectural issue or a result of
misuse by the end-user (opening multiple instances of the application in an attempt
to increase productivity).
Who is connected by SSMS?
Closely related to the previous script, Listing 2.4 focuses on those who are directly
connected to the SQL Server instances I support, via SSMS. If I see results that reference
a server-class box, I would be apt to question the activity. Red flags would also be
generated if I encounter rows that are not associated with workstations assigned to
DBAs, developers, or other authorized SQL Server professionals in my environment.
SELECT dec.client_net_address ,
des.host_name ,
dest.text
FROM sys.dm_exec_sessions des
INNER JOIN sys.dm_exec_connections dec
ON des.session_id = dec.session_id
CROSS APPLY sys.dm_exec_sql_text(dec.most_recent_sql_handle) dest
WHERE des.program_name LIKE 'Microsoft SQL Server Management Studio%'
ORDER BY des.program_name ,
dec.client_net_address
44