|
Archives of the TeradataForumMessage Posted: Thu, 27 Aug 2015 @ 15:55:07 GMT
I don't know if there were changes in ICU, TeraGSS or ODBC that might have a performance impact, but there shouldn't be any that would cause such a large impact. Have they made any changes to the table? New indexes, Join Index, other changes? If they are using ODBC ask them to try Teradata.Net instead. This is always the recommended connection method... and it is usually faster. I ran some tests myself. These only load 1000 rows (34 mostly Varchar columns) Note that since I connect over a VPN to a Teradata system 2000 miles away my times will be larger than for someone connecting over a local network. (This extra communication time may mask some performance issues - but not 6x issues) Version Connection Insert Time / Mode (Seconds) 13.10.0.9 ODBC 266 14.10.0.10 ODBC 285 14.10.0.10 Teradata.Net 186 15.0.0.6 Teradata.Net 175 15.10.0.2 Teradata.Net 174 15.10.0.3 Teradata.Net 160 * Not yet available Teradata Studio JDBC 495 Execute Parallel Teradata.Net 15 Import Teradata.Net 2 So I do see a small increase in time from 13.10 to 14.10 but this is more than offset if you switch to Teradata.Net instead of ODBC. (And using Import totally blows away the use of individual Insert statements.) It also appears that the 15.x versions are faster than either 13.10 or 14.0. If the customer is still having issues they will need to open an incident with GSC so that their specific issue can be looked into. Mike
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||