|
Archives of the TeradataForumMessage Posted: Mon, 22 Dec 2003 @ 14:19:07 GMT
Bill, Don't know about your first question. Second one: it depends on your transaction mode. By default sql is submitted under Teradata transaction rules, using implicit transactions. In this case, each of your statements below are treated as separate transactions, the lock(s) and any TJ rows for each transaction are released at the end of the transaction. So the delete/update rows are NOT kept in the TJ whilst the Select is running. Having said that, remember that the task which clears out the TJ is an asynchronous task (I'm not sure how often this runs) so strictly speaking the update/delete rows may be in the TJ when the Select starts. If these three statements are coded as part of the same transaction (either using Teradata BT/ET commands or because they're run under ANSI transaction rules) then the locks and any TJ rows will be kept in the TJ until the transaction ends. At this point, the locks are released and the TJ rows are marked for deletion (again the async TJ clear-out task will physically delete them 'at some point'). Cheers, Dave
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||