Archives of the TeradataForum

Message Posted: Thu, 27 Sep 2001 @ 13:10:39 GMT

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

Multiple sessions are created by Multiload anyway! The sessions command only specifies how many, as opposed to the default which is something like "The number of amps + 2" (ok, it's 7:00am, I don't remember right now). Whoa, if you've sorted the input file by the Primary Index, you COULD cause yourself a hot amp! Or rather worse, a rolling hot amp! Setting the sessions to one would ensure that you have reduced a massively parallel processing database to a non-parallel processing one! Why the heck do you want to do THAT? And why in anyone's right mind would you worry about the ORDER of updates? Uh, this is set processing, remember? The definition of relational, even the way SQL "thinks" about doing things is by sets. Let's hear what you want to accomplish, ok?

iv

Frank C. Martinez IV

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