|
|
|
Forum Newbie
Group: Forum Members
Last Login: Today @ 5:40:01 AM
Posts: 3,
Visits: 13
|
|
Not sure if this is the correct place in the forum for this question but here goes ...
We have a problem with a web based application written by another department which accesses our warehouse via OLEDB and is flooding our system with queries.
This application sends a query to the system and if it doesn't get a response within x seconds sends it again, leaving the original query still active and keeps doing this until it gets a response. Normally this isn't a problem as it gets it's response within the allowed timescale, but when our system is very busy (which it is quite often these days) it very quickly grabs all of the available sessions and blocks any other user running a query.
As we are struggling to get the department responsible for the rogue application to amend it, is there a way by which we can limit the number of sessions that any one User Id can have active at a time ?
We're running V2R5.1.
Thanks
Alistair
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: 11/12/2008 4:01:17 PM
Posts: 91,
Visits: 118
|
|
Have you investigated using priority scheduler? This allows you to place a ceiling on the amount of resources an application can have. Suggest you carefully read the "Teradata Performance Optimization" manual for V2R5.1 - specifically the chapter on priority schedulre. This document is available for download from Teradata.com.
Another option is to use ODBC connection pooling. More information is available in the Teradata ODBC manual also available for downloaed from the Teradata website.
|
|
|
|
|
Supreme Being
Group: Forum Members
Last Login: 11/12/2008 4:01:17 PM
Posts: 91,
Visits: 118
|
|
|
Also in v2r5 there was Teradata DQM Administrator (which in v2r6 was renamed the Teradata DWM. DQM will allow you to limit the limit the number of logons and the number of running queries for specific users or accounts.
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Today @ 5:40:01 AM
Posts: 3,
Visits: 13
|
|
Jeff,
Thanks for the replies, we're in the process of upgrading to V12 and will be introducing Priority Scheduler and DWM at that point.
We are trying to get the department that are in charge of the application to use connection pooling but are struggling to get them to do it, hence why we are looking for a way of doing it at the Teradata end.
I was just hopeful that there was a simple way to limit a user with what we currently have, but it looks like we haven't.
|
|
|
|