Archives of the TeradataForum
Message Posted: Thu, 17 Jun 2004 @ 19:34:35 GMT
| Subj: | | .Net App and Timeouts - persistent connection - PSF |
| |
| From: | | Rockarts, Steve |
I have a couple of question related to tactical queries and a persistent DB connection.
We have a client-side SOAP\XML application that makes us of a .Net Web Service application. This .Net Web Service application takes that
initial query, opens a web service instance, connects to Teradata using ODBC, uses several Teradata Stored Procedures, expanding on the query, and
returns the result set to the SOAP\XML application.
We have been experiencing some time-out issues and it appears that the logon to TD for each instance in the web service may be part of the
problem. We were wondering if anyone has any quick logon tricks or knows of a way to keep an instance of the web service open and process all
queries through that instance - a persistent connection - but - from what I understand, this is the way the web service works - it creates a new
instance each time?
Also, we have an account priority for the .net application logon account such that it has a PSF priority weighting only slightly lower than the
highest priority of our system resource partition - the way it should be. We were wondering if it is not getting a chance to really make use of
this tactical PSF weighting - considering that it must logon each time.
Any help would be much appreciated.
| 
