Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 22 Jul 2003 @ 14:54:06 GMT

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

Subj:   Re: OLTP Application Design Considerations
From:   Pradeep Patil

Hi Anomy,

Let me tell you frankly Teradata is not good for OLTP application, due to its parallel processing architecture. But if you are not inserting or updating many rows then its ok. Type 4 driver is best decision. While designing OLTP application you have to take into account following few points

1) User should not lock table otherwise this will add wait time on another user.

2) Dead lock should not occur.

3) It should support multi-user.

4) How critical is your data. When should you rollback.

5) How often you need to collect statistics

6) How many inserts and update in one cycle.

7) Does primary index available for updating table.

8) Performance

Handling all transactions with stored procedure is best choice. You can do manipulation on data in volatile or global temporary table. If you want more information let me know. I am working on J2EE (IBM Websphere) - Teradata application for last 1 & half year.



  <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