According to the Help, the RequestTiming server option controls whether or not several properties are recorded or not, including (for example) the connection-level ReqCountActive property.
However, this appears to not be the case for ReqCountActive in 220.127.116.112, plus others...
select property ( 'RequestTiming' ) AS a, connection_property ( 'ReqCountActive' ) AS b, connection_property ( 'ReqCountUnscheduled' ) AS c, connection_property ( 'ReqTimeActive' ) AS d, connection_property ( 'ReqTimeUnscheduled' ) AS e; Test 1 values are not NULL... a,b,c,d,e 'No','543','542','950.78711352705','.156981241973538' Test 2 values change... a,b,c,d,e 'No','548','547','950.787889712401','.157067199690039'
asked 24 Sep '13, 16:19
This behaviour could be appearing because changes to the server option ‘RequestTiming’ are effective only for new connections (for the duration of that connection)