Use SQL Server Profiler to track Databases

1. Find SQL Server Profiler and log on

Location: Click start -- program -- Microsoft SQL Server -- performance tool -- SQL Server Profiler

Or find the location after Logon:

2. Then, enter the following interface:

Enter relevant information and click Connect to enter the next interface.

3. interface as shown in:

4. The key points are in "Event Selection", for example:

Note:

Pay attention to the use of "column filter!

We can filter the statistical fields and click any column title to view the description of the column, as shown in:

Details:

To filter out the specific column name values, select the corresponding column, enter the specific values in the tree on the right, and select rows that do not contain values.

The meanings of each option are as follows:

TextDate depends on the text value of the event class captured in the trail;

ApplicationName: the name of the client application connecting to SQL Server. This column is filled by the value passed by the application, rather than by the displayed program name;

NTusername Windows user name.

LoginName user's login name (SQL Server Security Login or Windows login creden, in the format of "domain \ User Name ")

The CPU time (in milliseconds) used by the CPU event ).

The number of times that the server Reads the Logical Disk from the event.

The number of times the Writes event is written to a physical disk by the server.

The time used by the Duration event. Although the duration of the Server is measured in microseconds, SQL Server Profiler can display this value in milliseconds, depending on the settings in the tools> Options dialog box.

The process ID of the SQL Server application called by ClientProcessID.

SPID: the ID of the Server process allocated by SQL Server for the client-related processes.

The start time of the StratTime event (if available.

The end time of the EndTime event. This column is not filled with event classes that indicate the start of an event (for example, SQL: BatchStarting or SP: Starting.

BinaryData depends on the binary value of the event class captured in the trail.

Click Run!