Connection Pooling with Visual Basic .NET
Teradata Teradata Discussion Forums Teradata.com Discussion Forum
Visit Teradata.com
Home       Guidelines    Member List
Welcome Guest ( Login | Register )
        


This online forum is for user-to-user discussions of Teradata products, and is not an official customer support channel for Teradata. If you require direct assistance, please contact Teradata support.


Connection Pooling with Visual Basic .NET Expand / Collapse
Author
Message
Posted 3/21/2006 10:44:10 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 11/19/2008 2:41:24 PM
Posts: 15, Visits: 2
Hey everyone, I have run into some issues while connecting to Teradata through .NET

It's my understanding that .NET doesn't maintain a single connection to Teradata, it might open several connections when querying the database. This isn't a problem until I start using volatile or global temp tables. If I don't execute all the commands within the same sql statement, then it will not recognize the volatile table.

Is there any way to force .NET to only open one connection, and maintain that connection throughout the life of the connection? I've tried messing with the connection pooling properties, but still haven't been sucessful. Has anyone had any luck with this?
Post #3792
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 1 ( 1 guest, 0 members, 0 anonymous members )
No members currently viewing this topic.


All times are GMT -5:00, Time now is 12:24am

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.047. 7 queries. Compression Disabled.