Archives of the TeradataForum

Message Posted: Fri, 09 Mar 2007 @ 09:32:56 GMT

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

I am not entirely sure but there seems to be a couple of things going on here that are being ignored.

1. Just because the compile of the stored procedure fails due to YOUR ERRORS, does not mean that the compiler failed. The compiler did its job just fine. The return code from the compiler is 0. In other words, it did not abort.

2. A stored procedure is compiled (not Teradata directly) to run only when called. If you put bad SQL or SPL into a procedure and compile it will not compile. However, it seems from what you say that as long as the SQL is proper syntax - the compiler is not talking straight to a PE, which is not talking to an AMP, which is not bothering to look into the data dictionary. Maybe it assumes you know what you are doing. If you think about it - you can build a macro with improper SQL - write a select with aggregation and a non-aggregate - omit the GROUP BY and you get a macro. At the same time, Teradata is storing and validating the objects - but that is all. So, when you EXEC the macro - 3504 error message.

Just a couple of thoughts on the topic,

Michael Larkins
Certified Teradata Master
Certified Teradata SQL Instructor

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