Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PRINT OUT/DBMS_OUTPUT.PUT_LINE 1
- Thread starter DFW1999
- Start date
- Thread starter
- #2
-
1
- #3
Hi,
Teradata supports PRINT in its stored procedures
The output of the PRINT command goes to the DBW DBS/IO window which requires privlegded Access to the teradata Server to run.
The Other way is to debug a Teradata Stored Procedure is to create your own Log table and log what you want into it and after the stored procedure completes
sel * from Logtable;
to see what went on during your script.
just remeber The first thing the stored procedure should do is Drop the log table's previous contents.
You can go so far as to make a stored procedure for inserting into the Log Table so that you don't have to rewrite the code ever time you write a new procedure.
These options are explained in Chapter 4 of Vol 6 of the SQL reference manual.
All manuals are available at
Teradata supports PRINT in its stored procedures
The output of the PRINT command goes to the DBW DBS/IO window which requires privlegded Access to the teradata Server to run.
The Other way is to debug a Teradata Stored Procedure is to create your own Log table and log what you want into it and after the stored procedure completes
sel * from Logtable;
to see what went on during your script.
just remeber The first thing the stored procedure should do is Drop the log table's previous contents.
You can go so far as to make a stored procedure for inserting into the Log Table so that you don't have to rewrite the code ever time you write a new procedure.
These options are explained in Chapter 4 of Vol 6 of the SQL reference manual.
All manuals are available at
- Status
Similar threads
- Locked
- Question