Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 24 Jan 2002 @ 17:10:00 GMT


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


Subj:   SAS/Teradata performance considerations
 
From:   Doug Sedlak

Withers, Bethany wrote:

  Is anyone using the SAS interface with teradata, specifically the Warehouse Administrator, Enterprise Guide or Enterprise Miner tools? The SAS sales people are here trying to convince our user community that their tools will make their lives much easier(and may), but I am worried about performance, monitoring usage, normal DBA things, etc. I would love to hear war stories on the good, bad and ugly. If you would like to contact me directly, please do so.  



Beth,

SAS tries to integrate these products to produce the most efficient interaction possible between SAS and Teradata. SAS/ACCESS to Teradata is the component that produces the SQL passed to Teradata for table queries, normal inserts, FastLoading, etc. If you search the web (Yahoo search, Google search, etc) for "Teradata White Paper", you will find detailed information. As with any product, there are scenarios where users can "hurt" the DBMS by unleashing runaway queries. In view of this, the white paper describes possible negative scenarios and well as the good stuff, and also helps define "best practices" using SAS with Teradata. Probably the most important bottom line is for SAS users to constrain the amount of data they retrieve from Teradata (i.e. applying good programming practices). For SQL SAS generates, this means applying SAS WHERE clauses and subsetting the columns returned with SAS's DROP= or KEEP= dataset options. Or SAS users can craft the Teradata SQL themselves ("explicit SQL") and likewise limit the data returned with Teradata WHERE clauses and SELECTing only the needed columns.

Also, new releases of Teradata (V2R4 and higher, I believe) include the TDQM query manager as part of the DBMS, which can be used to contain problem queries for both CLIv2 and ODBC applications. Formerly only DBQM was available to manage ODBC connections. SAS/ACCESS to Teradata is a CLIv2 level application.


Doug Sedlak



     
  <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