And the connection method is irrelevant...same behavior whether connecting via ODBC or Teradata. It tough to diagnose a fix for an issue that cannot be recreated because of what looks like a Teradata bug.
↧