> > The tracker referenced here is not clear on how the MON$STATE > > represents CPU usage. > > MON$STATE = 1 implies that the statement is executing inside the engine at > the moment, so *supposedly* it consumes CPU (although it may be waiting > for a lock, for example). In turn, MON$STATE = 0 and MON$STATE = > 2 means that the statement is not being executed at the moment, so it > cannot consume CPU. > > As simple as that, nothing more.
But the case refers to reporting *CPU utilization/time* and the case details does not say what part of the case was implemented -- that needs to be clarified. Sean
