Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 27 Jun 2001 @ 22:09:26 GMT


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


Subj:   Enforcing Standards
 
From:   Anomy Anom

<-- Anonymously Posted: Wednesday, June 27, 2001 16:07 -- >

Actually my company is well-known for its standards. We use Sablime (from Lucent) for code change control and that was my work around to resolve the problem.

We never hard-code the database in our macros. Therefore using Sablime, the macros (over 3000 of them) are easily portable to other databases, especially since we have 4 test databases that the code must move through. The database is hard-code in the views on Teradata but not in Sablime. We have script generators that will insert the database name into the view creation script. The ids default to the proper database, therefore the user does not need to issue a database statement.

In the event of a real disaster, the recovery database would have the same name and be identical to production. But this was not possible for testing purposes, therefore the DR test is not a true exercise of our recovery procedures.

btw, we are also an OLTP shop.



     
  <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: 27 Dec 2016