Archives of the TeradataForum

Message Posted: Thu, 10 Nov 2005 @ 16:28:46 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

We turned on SQL tracing on a development environment and had MicroStrategy attempt to update the table definition for it's metadata. It's using the help column command. The "issue" seems to arise as the Max Length is reported as twice the length the table definition would indicate as the CASE statement is returning UNICODE. The Format in the help column command reports the column as X(10) but Max Length is 20.

MicroStrategy then takes this information and when it's creates volatile tables it will create a table as CHAR(20) instead of CHAR(10). Not the end of the world, but our Operations people think it could cause performance/spool issues and are making us move to COALESCE instead (which is viable for the majority of the cases that we are using CASE for, but not all the time).

At this point I'm not entirely certain if it's a Teradata issue or a MicroStrategy issue. I'm satisfied that we have an answer as to why it's doing it (CASE retuns UNICODE whereas COALESCE returns ANSI) so I can mitigate it. Would have been nice to know upfront though :-)

Mike

	<Prev	Next>		<<First	<Prev	Next>	Last>>