by Stephen Sing » Fri, 14 Dec 2001 01:45:08
Some trace events have not been reported to SQL Profiler because the
server has reached its maximum amount of available memory for the
process.
I am trying to find out if this message is refering to a SQL Server
process that could cause performance issues or if this is at the O/S
level, or something else.
Thx a lot
Stephen
by Jun Chen[M » Sun, 23 Dec 2001 17:43:44
Although you have the SQL Server 2000 SP1 applied, the following article
may help you understand the cause. Better check your SQL Server Errorlog
and see if there's a problem within the SQL Server.
http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q294976
Jun Chen
This posting is provided "AS IS" with no warranties, and confers no rights.
1. profiler cannot save all of textData column to file or db table
The TextData column of the profiler hold the sql statement for a given RPC
or whatever. Unfortunately, when you save the trace to a file for db table,
the data in the textData column is truncated. Pretty bad. Im am profiling
and loosing most of the where clause when I save. Any ideas?
-Alan Berezin
2. Paradox 7 reports and forms
3. Connecting to a Sql Server 2000 SP3 from a Sql Server 2000 SP2
5. Strange Behavior in Profiler in SQL 2000 SP1 and SP2
6. FPW 2.6 trouble with copy to -> ASCII-File
7. SQL Profiler Truncation of Textdata - Resolution
8. LONDON - SYBASE DBA - Derivatives Front Office - Unix/NT - to ￡100k package
9. SQL Profiler TextData Display
10. SQL Server 2000 SP2 and Windows 2000 SP3
11. Order by bit columns ASC 1 comes before 0 (SQL 2000 SP2)
12. Found Different Message in 'Textdata' column of SQL Profiler
13. SQL Server 2000 and SQL Profiler