What's a Thick transaction? [img]/images/graemlins/confused.gif[/img] No such thing.
Yes, they are adding up the cummulative number of transactions.
Long, rambling explaination:
Data thinning means removing some of the datapoints to reduce the size of the results collected during execution. If you leave the default Timing option the data collected is every second for the counters (including transactions) but collecting all datapoints for checkpoints. The data is all captured and reported, but you will have less records than the actual number of data if you have data thining enabled.
For example, with the default counter data thinning in Conductor, when you view the resulting default reports, they will show all the actual transaction counts. But when you manaully view the detail data for script counters # of transactions you will (most likely) see that there are less records than the actual number of transactions. So the cummulative # of transactions between records is greater than 1. I haven't experimented with it, but I believe if you turn counter thinning off that there would be 1 record for every transaction.
Also, graphs are limited to 1024 data points by default which is in the Analyze options dialog, data thinning tab. They say this has to do with screen resolution but you wouldn't see a difference unless you had more datapoints to graph than your screen resolution.
A problem is a difference between what is perceived and what is desired, that
we want to reduce (Dewey 1933)