Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Sat, 10 Mar 2007 @ 16:56:13 GMT


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


Subj:   Re: Exiting on BTEQ errors
 
From:   Jeff Jones

Set statmntout to a viable message on error, if you can't even errorcheck bteq are you sure you should be writing stored procs?

We recently allowed (accidentally I might add) some users to build procs and they ended up with over a hundred lines of code to insert one row and that was part of a ridiculous number of inter-dependant procs that caused a machine restart each time they tried to run it. (I know it shouldn't but we ended up just shunting the lot to ncr to find out why)

Be careful with procs, what's wrong with a good old fashioned batch job?



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020