?????? ??????This article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This event
indicates that a cursor on an SQL statement has been prepared by using ODBC,
OLEDB, or the DB-Library.
Error and Warning
Missing Column
Statistics
This event indicates column statistics that might have been
useful for the Optimizer were not available. The???column shows the list of columns with missing statistics. This
event, in conjunction with aMisc: Auto-UpdateStatsevent, indicates that theAuto Create Statisticsoption was triggered.
Misc.
?????
This event indicates that
an attention signal was sent by a client.
Misc.
????:-UpdateStats
This event
indicates that theAuto Update
Statisticsoption was triggered.
This event
indicates that a connection existed when the SQL Profiler trace was
started.
Stored Procedures
SP: Completed
This
event indicates when a stored procedure has completed execution.
Stored Procedures
SP: Recompile
This
event indicates that a stored procedure was recompiled during execution.
Stored Procedures
SP: Starting
This event
indicates when a stored procedure has started execution.
Stored Procedures
SP: StmtCompleted
This
event indicates when a statement in a stored procedure has completed
execution.
TSQL:
SQL:BatchCompleted
This event
indicates that a Transact-SQL batch completed. The???column shows the statement that was executed.
TSQL:
SQL:StmtCompleted
This event
indicates a Transact-SQL statement completed. The???column shows the statement that was executed.
TSQL:
RPC: ?????
This event indicates
that a remote procedure call (RPC) has completed.
If your application is receiving timeout errors, stops
responding (hangs), or experiences other events that cause the problem
statements to never complete, also include the following events:
243589
(http://support.microsoft.com/kb/243589/EN-US/
)
HOW TO: Troubleshoot Slow-Running Queries on SQL Server 7.0 or Later
To help identify the query that received the
attention signal, revise the trace so that it is not grouped by any data
column, and filter on the system process ID (SPID) that received it (on the??????tab, set SPID =x). TheSQL:StmtStarting,SQL:BatchStarting??,SP:StmtStartingevent immediately preceding the attention signal is the query
that received the timeout or cancel. You can search the????? ????column for the Attention event to easily locate it (on the?????????? ??,??????).
PREPARE SQL and EXEC
PREPARED SQL
ThePrepare
SQLevent indicates that an ODBC, OLE DB, or DB-Library application
prepared a Transact-SQL statement ,or statements, for use. TheExec
Prepared SQLevent indicates that the application made use of an existing
prepared statement to run a command.
Compare the number of times
these two events occur. Ideally, an application must prepare a SQL statement
one time and run it several times. This saves the Optimizer the cost of
compiling a new plan each time the statement is executed. Therefore, the number
ofExec Prepared SQLevents should be much larger than the number ofSQL ????? ????events. ??? ?? ??????SQL ????? ????????? ?? ?????? ?? ?????? roughly ??Exec SQL ????? ?????????, ?? ?? ???? ?? ????? ?? ????????? prepare/????????? ???? ?? ????? ????? ????? ???? ???? ??? ??????? ???? ?? ?? ??? ????????? ???? ?? ??? ???? ???? ?? ?? ?? ??? ?? ????? ???? ?? ??? ???? ??? SQL ??? ?? ?????? ?? ??? ?? ?? ???? ??? ???? ??????? ?? ??? SQL Server 7.0 ???????? ?????? ??? "????? ?? ??? ?? SQL ???" ???? ?? ??????
?? ????? ??????????? ?? ?? ????? ?????? ????? ????? ?? ??? ???????? ?? ??? statistical ??????? ?????? ???? ?? ?? ?? ????? ???? ??? ?? ????? ???? ?? ?? ?????? ???? ?? ?? ?????? ????????????? ?? ?? ?? ?? ?? ?????? ????? ????? ???? ??? ?????? ??????????? ????, ?? ???? SQL ????? ???? ?? ?? ?? ???? ??? ????? ??? ?????? ????? ?? ??? ??? informed ?????? ???? ?? ??? ????? statistical ????? Outcome ?? ?????? ????? ????? ???? ?? ???? ?? ????????? ?? ??? If you see these events, look at the query and the execution plan
generated, and then see the following article in the Microsoft Knowledge Base
for steps to take to improve the performance of this query:
243589
(http://support.microsoft.com/kb/243589/
)
HOW TO: Troubleshoot Slow-Running Queries on SQL Server 7.0 or Later
??? CPU ????? ????, CPU ?? ????? ?? ??? ??? ???????? CPU ??? biggest ???????????? ?????? ????? ??????"???" ?? ?????? ???????? ????? ???? ????? ?? ??? ?? ???????? ?? ????? ?? ??? ?? ?? ????? ?? ??? "????" ?? ??? ?????? They are more CPU and memory intensive than a nested
loop join, which is generally IO intensive.
If disk IO is the
bottleneck, group by reads and writes. ?????????????? ?? ???,NT User Name, ??SQL User Namefields to help isolate the source of a long-running query.
The integer data column of the exception event will indicate any
errors that were returned back to the client. You can find the text of the
error message by searching on the number in SQL Server 7.0 Books
Online.
Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
????? ?? ???? ????
???? ?????? ????????
