Archives of the TeradataForum
Message Posted: Mon, 05 May 2008 @ 12:03:48 GMT
This is one of those "you need to supply a bit more information" things.
With the (non) information you have provided there are really only 2 (generic) options to reduce the I/O count:
1) Tune the query/environment so that your query runs more *efficiently*.
2) Delete some data from the table.
The options for tuning a query and/or its environment are extensive. The options you would employ will vary depending upon the individual circumstances of the query you are trying to make go faster.
There is probably a 3rd option - which isn't so much about reducing the I/O count. You could upgrade and distribute the workload over more nodes. This assumes you don't have a hot AMP situation which puts you squarely in option 1 territory.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|