Content Server 6 Server Tracing

September 5, 2007 at 10:37 am | Posted in D6, Troubleshooting, Xense Profiler | 3 Comments

Loads of D6 documentation is appearing on Powerlink. I’m going through the Content Server Admin Guide over the next few days and I’ll pick out some of the stuff that looks interesting. The first thing that caught my eye was that Tracing and Logging has its own chapter. Previously this was all lumped into the Tools chapter. A very timely revision.

2 important changes here, first sqltrace is now on by default. This means that all the SQL being generated from a DQL command (very often there is a 1-to-many relationship between DQL and SQL) is output to the content server session log. I think this is a great improvement from the troubleshooting and performance tuning aspect.

Secondly there is a new server tracing option called rpctrace. The documentation states ‘Turns on tracing of RPC calls’. I will be having a look at the tracing format and the information being dumped by this trace option as again it is potentially very useful.



RSS feed for comments on this post. TrackBack URI

  1. oops … rpctrace option is introduced with SP4.

  2. Absolutely correct, my mistake. It was buried away in the 5.3SP4 release notes. Having had a look at rpctrace I’m not really so excited, it only records the name of the RPC not the arguments involved. Also not all RPCs actually get recorded – for example the next() rpc to access the next batch of results for a collection doesn’t appear to get recorded.

    The 5.3sp4 release notes did point out that the Content Server sqltrace now includes a session ID and Database ID which does look useful.

  3. Despite the notes in the Admin manual I don’t find that sqltrace is on by default. Probably a good thing, just imagine all the disk writing going on when large numbers of users are accessing the Content Server and causing queries to be submitted to the database. DQL often creates more than one SQL statement so this could be an even bigger number of SQL than you think.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Blog at
Entries and comments feeds.

%d bloggers like this: