|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Server 2005 Lost Profiler EventsIn SQL Server 2005, is it possible for the SQL Server profiler to miss
events? This was the case in SQL Server 2000 in a heavily used environment. The fix was to do a server side trace. Does the same problem exist in SQL Server 2005? Cgal (cgallelli@newsgroups.nospam) writes:
> In SQL Server 2005, is it possible for the SQL Server profiler to miss One would surely hope so, or else a trace with too many events over > events? This was the case in SQL Server 2000 in a heavily used > environment. The fix was to do a server side trace. Does the same > problem exist in SQL Server 2005? a slow line could bring a server to a halt. -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx Yes, Profiler is not intended to be used for your production applications.
That is why you have server side traces. It can lose events and drastically slow your server down. A nice change in SQL 2005 is that you can use Profiler open up the file you are using to capture the server side trace, even while the trace is running. Show quote "Cgal" <cgallelli@newsgroups.nospam> wrote in message news:OszoJZq%23GHA.3456@TK2MSFTNGP02.phx.gbl... > In SQL Server 2005, is it possible for the SQL Server profiler to miss > events? This was the case in SQL Server 2000 in a heavily used > environment. The fix was to do a server side trace. Does the same problem > exist in SQL Server 2005? >  |
|||||||||||||||||||||||
Other interesting topics