Archives of the TeradataForum
Message Posted: Thu, 11 Jun 2015 @ 16:40:23 GMT
Are you testing this using JDBC or through a test app like SQL Assistant?
This is a known problem with .Net applications that fetch data through ODBC. (A major reason we always recommend that you connect using Teradata.Net instead.)
The issue is within the Microsoft .Net Provider for ODBC layer so there is no way around it.
If you are testing your procedure using SQLA (or any .Net app) you must use a Teradata.Net connection.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|