• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1004
  • Last Modified:

Teradata truncating character fields when updated from Access

I'm trying to run a simple append query in Microsoft Access.  The query selects 3 character fields in a local table and appends them to a linked table (via ODBC) on a Teradata server - no where clause, conditionals, or data transformation.  The structure of the fields in the linked table is equivalent to that of the local table, as far as I can tell.  Local table has text fields of length 11, 15, and 15 characters; Teradata table has corresponding Varchar fields of length 11, 15, and 15.

The query completes successfully... but the resulting data in the Teradata table is truncated to half of the character length of the field. For example, a text value 'Enterprise' in the first field in the local table is stored in the Teradata table as 'Enter'.   This is consistent for all the character fields.  I tried an integer field as a test; this appears to append successfully without any truncation.

Is there some encoding issue I need to be aware of when moving data between MS-Access and Teradata?
0
Mckenzma
Asked:
Mckenzma
  • 2
  • 2
1 Solution
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Possibly this:

See this link:

http://allenbrowne.com/ser-63.html

mx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Make sure your TeraData engine is storing as Unicode ...
0
 
MckenzmaAuthor Commented:
How can I tell if the TeraData engine is storing as Unicode?
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
I have no idea; I'd assume there is some sort of management interface for the TeraData db (something like Enterprise Manager for SQL Server) where you could determine how the db is storing data.
0
 
MckenzmaAuthor Commented:
I found something that worked.  In the ODBC Data Source Administrator, I changed the session character set for the Teradata db from ASCII to UTF8.   The full character values are now stored in the Teradata db when I run the query.

Strangely, this change has destroyed my ability to browse linked Teradata tables from Access.  Every field displays "#Deleted".  Not of immediate importance to me... but curious.

I'll award the points.  Thanks for the idea.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now