ScottMattes
Member³
As ask by a co-worker:
When doing some performance fixing in PL/SQL Developer, it's usually because some statement is taking forever. If left alone to run until it finishes, PL/SQL Developer will tell me how long it took. However, sometimes I don't want to wait that long and kill it after 10 minutes, or whatever.
Does PL/SQL Developer have a "running clock" feature in it, that tells me how long it's been running so far, or perhaps a "started at" time?
I told him "NO" and "YES". I'm thinking that at least for the "started at" time, there should be some system view that knows that.
When doing some performance fixing in PL/SQL Developer, it's usually because some statement is taking forever. If left alone to run until it finishes, PL/SQL Developer will tell me how long it took. However, sometimes I don't want to wait that long and kill it after 10 minutes, or whatever.
Does PL/SQL Developer have a "running clock" feature in it, that tells me how long it's been running so far, or perhaps a "started at" time?
I told him "NO" and "YES". I'm thinking that at least for the "started at" time, there should be some system view that knows that.
