Archives of the TeradataForum
Message Posted: Fri, 18 Apr 2003 @ 13:51:40 GMT
| Subj: || || Re: Improving performance of Bteq Export |
| From: || || Judge, James A |
Once you've established a baseline "datapoint" of export bandwidth (without knowing BTEQ platform and Ethernet speed I would guess at 2-
3MB/sec) you can look at breaking up the result into more than one stream (session). This obviously assumes the baseline is a single
session SQL request. But there is limited (if any) benefit to using a multi-session approach as the number of sessions versus the ability
to not do FTS (full table scan) with each session request. The idea would be to create an input file of a column/columns values to allow
multiple-sessions to each submit the SQL but the WHERE clause contains the input variables to segregate the output X number of pieces. Since
each request is most likely a FTS the increased overhead of executing all X (say 5 as an example) will probably negate any benefits.
Not really having done much testing with this you could try changing the "response buffer" size in the clispb.dat (rsplen=8192 is the
default ; can be set to 64K). See pg 3-133 of the "Teradata Call Level Interface Version 2 for Network Attached Systems".