Re: ODBC

The specifications for a .NET data provider calls for the implementation of
a connection pool. Each provider does this somewhat differently, but I
expect the Teradata provider is no exception. This means that the overhead
imposed when opening (closing) and reopening connections should be
minimized.
While working with ASP applications you really don't have a choice--you
must open and close connections constantly. However, there are other choices
if you're building a Windows Forms application. In this case it's perfectly
okay to open the connection and leave it open for the duration of the
application--assuming that the Teradata does not have some other restriction
on the number of connections applied.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"marcmc" <marcmc@discussions.microsoft.com> wrote in message
news:C22F7FE2-DC2B-455B-936D-ED2E2F46927E@microsoft.com...
> Hey,
>
> What do people/gurus think of ODBC connections to databases?
> The beauty of .net is it allows the database to only be connected to for
> the
> length of time you need it. This is great for classes like SQLClient and
> OLEDB.
> However, I'm quite worried that my use of Microsoft.Data.odbc.dll to
> connect
> to Teradata will impose application performance issues(it takes 20
> seconds)
> by constantly connecting/disconnecting/connecting again etc.
>
> Does anyone know for sure that the .NET Provider for Teradata is only
> compatible with VS 2005?
>
>