Archives of the TeradataForum
Message Posted: Fri, 14 Mar 2003 @ 20:15:08 GMT
We did use bteq in both environments. We created a .sql file with the stored procedure. We ran the script in development, tested the results and migrated the same script in production. And, that is when we started having problems.
We broke down the stored procedure in production into three smaller parts and the pieces ran fine. However, when we call the procedure, teradata seems to complain. I was wondering, if the sql script was too large and if the parser chopped the script somewhere in the middle.
Is this possible? If so, is it caused by an server setting?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|