Archives of the TeradataForum

Message Posted: Tue, 30 Oct 2007 @ 17:29:27 GMT

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

I also suggest that you disable parsing (clear the checkbox for 'Allow use of SQL Extensions') unless you specifically need the feature.

The only times you should need it are if your application actually inserts ODBC extensions (such as "{d '2007-10-21'}" instead of a date literal) or you are creating a stored procedure. (This latter one applies only to Teradata as far as I know.)

I'm not aware of any probles with calling functions or Altering tables (with the option cleared) so long as you enter valid Teradata SQL for these. If however you are entering ODBC types and expecting the driver to change them to Teradata types then it would need to be checked. (Definately not something I would recommend. In fact the main reason I suggest clearing the option is that if you don't clear it then the driver may change your data types without you realizing it has done that.)

As to your original problem, I dont know why preceding your queries with a comment would cause the query to fail, unless:

a) You are using the 'single line' comment delimiter '--'

and

b) You are using an old ODBC driver

The '/* ... */ style comments should work OK, and newer drivers allow '--' style comments even if they occur before the first statement.

One possibility I can see is that if you enter your GUID with "{}" around it the ODBC driver might think that it is an ODBC SQL Extension since braces are used to delimit the extensions. However I tried entering the following line before my SQL:

-- My Report | {831FDD16-0C5C-11D2-A9FC-0000F8754DA1} | Mike

and it ran fine. (I used SQL Assistant 12.0 with ODBC 12.0 however)

Mike Dempsey
Teradata Client Tools

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