Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Trace   (RSS)
Friday, January 23, 2009 10:10 PM

INF: Multi-Machine Replay Using ORCA and OSTRESS

You can place ORCA on a central computer and allow it to control the sequencing from multiple client computers running OSTRESS.    To accomplish this you must configure the firewall properly. Note: Be sure to install the same version of
Posted by psssql | 0 Comments
Monday, January 12, 2009 11:14 PM

ReadTrace Generates Unexpected Connect Node - Not Really

At first glance it appears that ReadTrace has generated an unexpected connect node.  Upon closer inspection the behavior is correct in order to maintain the proper set options for the connection. Trace has both physical and logical connect/disconnect
Posted by psssql | 0 Comments
Thursday, January 08, 2009 5:51 PM

Filtering Trace Data Without Loading In Profiler or Database Table

We are often asked how to extend the filtering of RML (ReadTrace/OStress) or Profiler.  Filtering during trace production is the preferred method because it typically reduces the overall impact of the Trace on the SQL Server throughput.  
Posted by psssql | 1 Comments
Filed under: , ,
Tuesday, December 16, 2008 11:47 PM

How It Works: SQL Server No Longer Uses RDTSC For Timings in SQL 2008 and SQL 2005 Service Pack 3 (SP3)

Many of you have encountered the RDTSC timing variances that I outlined in an earlier blog post:   http://blogs.msdn.com/psssql/archive/2006/11/27/sql-server-2005-sp2-will-introduce-new-messages-to-the-error-log-related-to-timing-activities.aspx
Posted by psssql | 3 Comments
Wednesday, July 23, 2008 9:01 PM

How It Works: Attention, Attention or Should I say Cancel the Query and Be Sure to Process Your Results

I ran into this issue the other day and decided it would make a good post.  Since I have seen this issue more times that I can count I will again attempt to provide details. The attention event in SQL Server trace output indicates a query cancellation.  
Posted by psssql | 2 Comments
Wednesday, June 25, 2008 3:01 PM

How It Works: Trace (.TRC) File Security

SQL Server 2000 shipped with different trace file security than later builds of SQL Server 2000, SQL Server 2005 and SQL Server 2008. The SQL Server process (sqlservr.exe) writes the trace files to the specified destination.   The SQL Server
Posted by psssql | 3 Comments
Thursday, January 24, 2008 3:30 PM

How It Works: Conversion of a Varchar, RPC Parameter to Text from a Trace (.TRC) Capture

The Senior Escalation Engineers do various training and mentoring activities. As I do this I thought I would try to propagate some of this information on the blog. This was an interesting issue I ran into this week. The reported problem was that the data
Posted by psssql | 1 Comments
Sunday, August 19, 2007 4:46 PM

SQL Server 2005 - RDTSC Truths and Myths Discussed

I posted some updates to my blog entry about the RDTSC and drift warnings in May. See the following link http://blogs.msdn.com/psssql/archive/2006/11/27/sql-server-2005-sp2-will-introduce-new-messages-to-the-error-log-related-to-timing-activities.aspx
Posted by psssql | 7 Comments
Thursday, March 29, 2007 8:52 PM

SQL Server 2005 SP2 – Trace Event Change – Connection Based Events

Starting with SQL Server 2005 SP2 the connection based events are also produced for sp_reset_connection activities, indicating the connection was reset. The pattern will look like the following. RPC:Starting sp_reset_connection Disconnect Subclass = 2
Posted by psssql | 3 Comments
Filed under: , ,
Monday, November 27, 2006 5:54 PM

SQL Server 2005 SP2 will introduce new messages to the error log related to timing activities.

The following article has been publiched about this subject: http://support.microsoft.com/kb/931279 RDTSC Drift vs Not Synchronized To clarify - SQL Server 2005 SP2 contains both Drift and a Non Synchronized warnings. The Non Synchronized message is only
Posted by psssql | 6 Comments
 
Page view tracker