Archives of the TeradataForum

Message Posted: Tue, 08 Sep 2009 @ 08:41:29 GMT

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

Hi,

The MaxLoadTasks parameter is there to allow you some control over your Teradata environment. By limiting the number of Fastload/Multiload/Fastexport tasks ("Loadtasks") running concurrently then you prevent such processing from (possibly) using all cpu resources and allowing none for other concurrent work.

Do you ** have ** to use this parameter ? No. If any concurrent work runs in an acceptable time then I don't see any point in limiting the number of Loadtasks.

Also, remember that the system limit for the number of Loadtasks is independent of the system configuration. The default system limit is 15 and is the default number of combined Loadtasks that can run concurrently.

With V2R6 a second parameter was introduced (MaxLoadAWT) which allows you to run more concurrent Loadtasks. Look in the "Utilities manual - G - F" for details.

Again, whether you want to run more than this is dependent on what your load jobs are doing (i.e. how much work) and what other work is running concurrently and whether that concurrent work is meeting it's target processing time.

Regards,

Dave

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

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