Archives of the TeradataForum
Message Posted: Thu, 30 May 2002 @ 14:43:36 GMT
I have to agree with John. We had a similar situation here with a campaign management tool. The software was submitting sql "prepares" excessively, sometimes as many as 20 times per actual query (once for each condition in the where clause).
Additionally, as the user moved through the query builder canvas, the software repeatedy checked the validity of tables with prepares. Tables, btw, whose metadata information was already stored in the tool's repository.
It took a lot of griping, but eventually, the vendor modifed the tool to turn off these prepares. This made our life a lot easier, as our accesslog was now only filled with queries that actually were executed, and we only took the PE hit once. This is important as we are almost always CPU, rather than IO bound.
David W. Roth
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|