| Sudipto Chowdhuri 2005-10-28, 1:24 pm |
| Hello all,
I want some input from you folks on a problem
and the solution that we're proposing. This is related to QP
metrics, a new feature in 15.0, whereby we can capture all
queries in an application into a system catalog along with
all kinds of execution metrics. The problem is that this
causes catalog bloat and we may run out of space. One
obvious thing is to filter out what we want to store. It may
not be appropriate to save "low cost" queries. The problem
is how do we define "high cost" queries. The metrics that we
have are:
- exec time (min/max/avg)
- lio (min/max/avg)
- pio (min/max/avg)
- user id
My questions are the following:
1. Do you think we could just use two config parameters, one
for avg exec time and the other for avg pio time and use an
OR semantics ?
2. Config parameters are a bad idea and you would like to
see a stored procedure where we say
sp_blah_blah @pio_threshold = k1, @exec_time = k2
3. Just a simple OR is not enough and you would prefer to
have the flexibility of using a combination of ANDs/ORs for
one or more user ids.
4. Would you prefer to have a session level filtering as
well ?
Thanks for your time,
Sudipto R. Chowdhuri
Sr. Staff Eng. (ASE Query
Optimizer)
-
|