 |
 |
Archives of the TeradataForum
Message Posted: Tue, 28 Sep 1999 @ 21:22:12 GMT
Subj: | | Re: Query Management |
|
From: | | Kenneth Stiglich |
I think that using that NCR tool or other you would know how much memory and I/O is using a specific query at running time, and you will
track the query execution to see his memory and I/O consume, but I don't think a possible way to estimate the time or memory need to run a
complete query. According with your mail I think that you are trying to classify every query prior to send that (or intercept the query)
and, in case of a short query run it, and in case of a large query for example, delay that to the night. The only way to estimate the time
for each query is running a explain prior to send it, but I don't think you will believe in the time that explain will give you.
Just Track every query,
Regards,
Kenneth Stiglich M
Serv. Data WareHouse
Ingenieria de la Informaci�n
| |