Archives of the TeradataForum

Message Posted: Wed, 13 Nov 2002 @ 18:51:08 GMT

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

A perfectly valid point. However may I add in a couple of things to the discussion so far:

Firstly even though an Insert/Select may be running or rolling back the users can still get to the data by using an ACCESS lock. I realise that this may not always be desirable, but the capability is there.

Secondly, you can generally add additional code to avoid hitting duplicate rows/index values etc and so avoid the common causes of rollbacks.

At the end of the day, what's the fastest way of achieving the required processing and business and operational goals (or at least an acceptable compromise of the last two)? Whatever way meets that lot will be the way that you decide to use. Sometimes it will be insert/select, sometimes it will be export/load.

Cheers,

Dave

Ward Analytics Ltd: Information in motion (www.ward-analytics.com)

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