[Info-Ingres] .NET Data Provider with Ingres 2.6

[Harrison, Mark]

Hello again Jim,

Thanks again for your reply. I have definitely tested using the Ingres
.NET Data Provider against Ingres 2.6 without a DAS (we have no 2006
installation here where I tested it). From looking at the dll, the .NET
Data Provider version appears to be 1.1 and I have been using a
connection string of "Host=my26host;Database=my26db;User
id=myuser;PWD=mypwd". I did try some variants specifing a VNODE however
they all caused exceptions (which you explained by saying we need a
DAS).

One of the small tests I did was to compare the speed of a select on a
large table using the .NET Data Provider and an ODBC connection.
Intially the .NET Data Provider was something like 5-10 times faster
(which I guess is expected) over the ODBC connection, however I just
tested it again now and the ODBC connection is significantly faster than
the .NET Provider. Strange.

Thanks for the example connection string and the info about requiring a
DAS. In the case of our application, the client machine never accesses
the database directly. All such access is performed by our middle tier
so I assume it alone requires the Ingres client installation and DAS.
Also, as long as we configure delegation and authentication properly,
the middle tier should be able to flow the clients credentials to the
database.

We may consider simply moving to Ingres 2006, although not sure what
other issues may arise.

Thanks again,

Mark.

-----Original Message-----
From: Jim Gramling [mailto:jimwgramling at gmail.com] 
Sent: Friday, 16 February 2007 7:09 AM
To: Harrison, Mark; info-ingres at kettleriverconsulting.com
Subject: Re: [Info-Ingres] .NET Data Provider with Ingres 2.6

Hi Mark,

> Thanks for you reply. I've been able to use the .NET Data Provider 
> against 2.6 using a connection string similar to your first version 
> (specifying Host, Database, User Id and PWD). I guess as we don't have

> an Ingres 2006 DAS we cannot use our vnodes (as you indicated below).

How are you connecting without an Ingres 2006 DAS?  Which .NET data
provider are you using (1.1 / 2.0)? and what values do you specify in
the Host and Port entries?  The native Ingres .NET data provider doesn't
support a direct connection to an Ingres DBMS (either 2.6 or 2006) ...
maybe you are using a .NET odbc provider with the Ingres odbc driver?

> What we are really trying to achieve is being able to connect without

>specifying User ID and PWD in the connection string (ie. Letting the  
>user's windows ID pass through to the database). I assume we still need

>a DAS with the VNODE setup with the installation logon, but not sure if

>this will work against Ingres 2.6.

The only way that you can do this (that I know of) is to have a full
Ingres 
client installation with a DAS server on each user machine.   You will
need 
to set an installation password in netutil on the server machine, and a
corresponding netutil entry on each client referencing the installation
pwd for the server host.  Test your installation password at the command
prompt before you try to connect with .NET.

To connect through the Ingres .NET provider, you can build a connection
string without the User Id and PWD entries: it should look something
like this

"Host=(local);Database=my26vnode::my26db;Port=XX7;Vnode_usage=login"

my26Vnode is the local vnode that points to the server host (with the
installation password), and Port is the listen address of the Data
Access Server on the local client machine (by default II7).  The local
windows logon user will passed through to the Ingres 2.6 server without
need for additional authentication at the server's OS level (of course,
the user must be a valid Ingres database user, authorized in accessdb or
vdba).  Note that this will work whether the remote server is 2.6 or
2006.

The only thing inconvenient about this solution is the necessity of
installing a bunch of Ingres clients; you lose one of the principal
benefits of using the DAS, which is an Ingres client-free connection for
the end user.  It might be easier just to force the user to login again
when entering the application: then all you need is an intermediate
machine with Ingres 2006 installed.

Regards,

Jim Gramling
Rio de Janeiro






NOTICE - This message and any attached files may contain information that is confidential and intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.