Archives of the TeradataForum
Message Posted: Tue, 15 Mar 2005 @ 03:48:42 GMT
This may be nothing and sound silly, but it has been known to be overlooked in the past.
Does the client workstation have a decent network connection to the Teradata?
For example, is the client workstation in an office block that is remote from the Teradata? If so, it is possible you are running over a "relatively" slow link. You might not notice the effect of the "bottleneck" until you run a job such as this update. The solution of course is to run the client from a workstation that is "local" to the Teradata - in network terms.
P.S. As a matter of interest, how long does your update take if you run it say via queryman with a where clause that targets roughly the same number of rows as the tpump update?
This is probably not a fair comparison, but might give a basis of comparison for how long it should take - especially if the N/W is an issue.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|