Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 10 Nov 2003 @ 20:53:11 GMT


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


Subj:   Re: How does queryman calculates the total number of rows?
 
From:   LeBlanc, James

Userid rmbsmd answered this question earlier by saying that the number is available in the success parcel.

Let me add a little more information to that response.

Queryman does not calculate the total number of rows in a response. All queryman does is to report the calculated number. The database itself calculates the total number of rows for all SQL responses. The total is created after all the final spool is created and is posted in the first message returning to the application (in this case queryman). The response is sent back from the parsing engine. This first message is actually a particle of a physical message. It is more of a control block and is properly called a response parcel. Many parcels make up a response block and many response blocks make a response. etc.

As the first parcel of a response block CLI, the client to database interface, returns one status parcel followed by other parcels. The one being discussed is the success parcel. It implies a zero return code and contains an activity count, which is a row count. In this case it is the number of rows, selected, updated, deleted, updated. It does not account for internally discarded rows. For example a select count(*) from table. Gives an activity count of 1, as a single count was selected. When BTEQ tells you how many records were processed, this comes from the activity count. The activity count is posted to SQLDA for precompiled programs.

There is much more detail on this. But I expect that for now this might over answer the question. You are welcome to ask more if you are so inclined.

Jim LeBlanc



     
  <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: 15 Jun 2023