Archives of the TeradataForum
Message Posted: Mon, 06 Apr 2015 @ 19:23:29 GMT
As pointed out, a "locking row for ..." does not necessarily mean that you get a row (or row hash) lock. You also have to have an equality constraint on the PI of the target table.
Note that an INSERT/SELECT will always place a table level write lock on the target table.
To get multiple transactions inserting rows into the same table concurrently whilst minimising lock contention you have to EITHER:
- each insert must be an INSERT VALUES command (i.e. insert a single row),
- have the data values outside of Teradata (e.g. in a file) so that each individual request processes a single row hash of the target table.
Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|