Archives of the TeradataForum
Message Posted: Fri, 12 Dec 2003 @ 19:08:08 GMT
| Subj: | | Re: Concurrent Loads/Deletes for Staging Table |
| |
| From: | | Duane Angle |
We're trying to avoid having to create a separate table for each country because of the overhead/maintenance involved. We are
separated where the MLOAD process is concerned for the initial staging of the data and would prefer not to maintain the split further
than that.
I'm not sure I'm understanding your second paragraph, so bear with me. The MASTER table has the Primary Index of Customer and
Material, but it does contain the Country_Cd and Month fields that we delete by as well. I'd just like to find a way to facilitate a
true row-level locking mechanism so that I can have 3 or 4 countries deleting their own rows from that MASTER table since there is
never an overlap from one country to the next.
Are you saying that a delete via a join would provide something along the lines of a row level lock (thus your suggestion for the
temporary table)? Or are you saying that adding the Country_Cd and Month to the PI on the Master table might cause Teradata to opt
against the table lock?
Thanks.
|