Comments on: Content Server 6 Server Tracing http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/ Documentum Internals and Performance Thu, 16 Jul 2009 12:58:50 +0000 http://wordpress.com/ hourly 1 By: Robin East http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-96 Robin East Thu, 27 Sep 2007 17:50:42 +0000 http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-96 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. 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.

]]> By: Robin East http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-87 Robin East Thu, 13 Sep 2007 15:52:22 +0000 http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-87 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. 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.

]]> By: msirfani http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-85 msirfani Thu, 13 Sep 2007 06:23:25 +0000 http://robineast.wordpress.com/2007/09/05/content-server-6-server-tracing/#comment-85 oops ... rpctrace option is introduced with SP4. oops … rpctrace option is introduced with SP4.

]]>