|
Archives of the TeradataForumMessage Posted: Thu, 03 Nov 2005 @ 19:10:03 GMT
Dustin, In addition to these and many other tuning efforts for transactional type work. If you really want to do this type of work with Teradata you should try to not to submit these sequentially but in parallel if the requests are not dependent. You can fire all of these requests off in parallel and try to overlap the run time. Although this may extend the run time of each request. That would depend on the requests themselves. If the requests are dependent on each other, you may try to push some of the work into a Stored Procedure to save trip time and leverage some of the dependent data into a sub-sequent request. Try not to use a standard Cursor approach without understanding the downside for each or any request. This does sound like transactional workload (Maybe not very decision making, but I don't know the application or the reason behind putting this on Teradata) I wouldn't discourage putting this type of requests on Teradata but if they are not high value requests then you will probably spend a fair amount of time just learning to tune for transactional work on Teradata, which may be a good thing in the long run for your own knowledge, your application, or even your Company. Good Luck, Eric
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||