Archives of the TeradataForum
Message Posted: Tue, 24 Sep 2002 @ 16:56:21 GMT
As you increase the number of concurrent and active sessions a single request will normally get a smaller percentage of the machine resources and therefore queries will run longer. However, I would not expect it to be 10 times longer if the only factor was running 5 concurrent queries. I suspect that there are other factors at play. You mentioned the possibility of loads occurring at the same time as the queries. Depending upon the priority of the load jobs these certainly could explain the difference. You will also want to verify that locks are NOT being applied to the table(s) you are attempting to read.
Additionally, you will want to check that each of the 5 queries insert into separate temporary tables. I believe that MicroStrategy automatically generates a unique table name for each query so this should not normally be an issue. However, if you have cut the query from the engine window and attempted to simulate the process under QueryMan you might be attempting to insert into the same table. In this case you will be holding a write lock on the temporary table.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|