97.

What are the main events and columns helpful in troubleshooting performance
issues using profiler?

SQL Profiler: if we run profile withput filtering required events it takes lot of
resources and capture lot of info that we dont neee. Before we start profiler We
need to choose the events that we want to monitor,select few columns that we need,
we need to filters only required databases, tables or sps based on our need.

Events:
Event Group: Performance
Event: ShowPlan_ALL (BinaryData column must be selected)
Event: ShowPlan_XML

Event Group: T-SQL

Event: SQL:BatchStarted
Event: SQL:BatchCompleted

Event Group: Stored Procedures

Event: RPC:Completed

Event Group: Locks

Event: Lock: Deadlock Graph
Event: Lock: Lock Deadlock Chain (Series of events that leaads to a
deadlock)

Event Group: Sessions

Event: Existing Connection
Event Group: Security Audit
Event: Audit Login
Event: Audit Log Out
Columns:

Below are the most common columns that help us in understanding the trace file to
troubleshoot the problems.
TextData
ApplicationName
NTUserName
LoginName
CPU
Reads
Writes
Duration
SPID
StartTime
EndTime
Database Name
Error
HostName
LinkedServerName
NTDomainName
ServerName
SQLHandle
All these columns need not be available for all of the events, but depends on the
event
select we have to choose the appropriate columns.

Filters:
ApplicationName
DatabaseName
DBUserName
Error
HostName
NTUserName
NTDomainName