Ingres 2.80 driver without VNODE

[wmSales]

Hey Folks.
I'm new to this board but not to Ingres.

Until now it was no problem, to get an Ingres-Driver runnning on (nearly) each kind of Win OS.
But now i've got a question.
I want to establish an connection to our Ingres-Server, WITHOUT installing the whole Inges-Environment.
Just to get the 2.80 driver working without creating any VNODE would be perfect suitable for me.

Is there any solution known about my Question?

Neither Google, nor boardsearch brought a solution to me.

please help. Thanks

[thoda04]

You don't need to install all of the Ingres components to use the Ingres ODBC driver. You only need the Ingres Networking (aka Ingres Net Client) on the client side.

Hope this helps,
Dave

[gerhard.hofmann]

It would be nice if Ingres could provide an ODBC driver that is as "lightweight" as the DotNet-DataProvider (ingres.client.dll) and the JDBC driver (iijdbc.jar). Both can directly connect to Ingres' Data Access Server.

Of course, Dave is right, only Ingres Net Client is needed on the client side for JDBC to work. Annoying: a service "Ingres Intelligent Database" is added to the system and you have to deal with Vnode entries.

Regards
Gerhard

[kschendel]

I agree, it would be nice, but also non-trivial. The current ODBC code uses the Ingres API which depends on Ingres-Net. Re-coding it to use (the newer) DAM protocol would probably be a lot of work. Community volunteers, anyone??

[wmSales]

Thanks.

Great job guys.
Thats what i wanted to hear

On Ingres.com i just found a .NET Dataprovider.
I'm quite sure, that is not what i need, isn't it?

Is there any directlink to Download?

[Bodo]

gerhard.hofmann wrote:

Annoying: a service "Ingres Intelligent Database" is added to the system and you have to deal with Vnode entries.

What is the annoying thing at the one-time service installation?
You can also remove the service (using "opingsvc remove <ProductName>") and start the iigcn and iigcc processes manually (e.g. using the "start" command with either /min or /b flag).
You also do not have to define vnode entries in advance, you can use a dynamic node definition in the ODBC connect string, e.g.:
"driver=Ingres;servertype=ingres;server=@myHostnam e,tcp_ip,II;uid=myUserName;pwd=myPassword;database =myDatabase"

[wmSales]

I must say that this is no satisfying solution.

Every DB-Engine i know, offers a simply Setup which just gives me a chance, to Access a Server by his Ip-Address or his Host-Name.

The devices i want a driver to be installed, should be *noob-safe*.

On the standardway, ingres2006 installation sometimes confuses even me! (Software-Engineer)

It would be fine, if someone could simply post a Download-Link to the above offered solution.

[gerhard.hofmann]

Originally Posted by Bodo

gerhard.hofmann wrote:
What is the annoying thing at the one-time service installation?
You can also remove the service (using "opingsvc remove <ProductName>") and start the iigcn and iigcc processes manually (e.g. using the "start" command with either /min or /b flag).
You also do not have to define vnode entries in advance, you can use a dynamic node definition in the ODBC connect string, e.g.:
"driver=Ingres;servertype=ingres;server=@myHostnam e,tcp_ip,II;uid=myUserName;pwd=myPassword;database =myDatabase"

I should have been more precise here. So here the things I find annoying:
#1: iigcc and iigcn must be started every time the workstation is booted, even if ODBC reporting is only done few times a month. In theory, user could run the ingstart.exe program only when needed, but I'm sure that is to complicated for typical user.

#2: sometimes Ingres variables get lost because of 0-byte symbol.tbl making the Ingres client unusable. OK, I must admit that problem seems to be only in old versions of the Ingres client...

#3: Ingres client becoming unusable because client hostname is changed. Not sure, that problem may have been solved with client > 2006, haven't actually tried

#4: adding Vnodes at a later time almost anytime will fail when the user is not identical with the user that installed the client. Error message, "user does not have privileges in config.dat..."
(and yes, I *know* how to fix the config.dat in such situations and I always hate it...)

Your hint with the (vnode-less) ODBC connect string sounds helpful, will try this.

Regards
Gerhard

[Bodo]

#1: iigcc and iigcn must be started every time the workstation is booted, even if ODBC reporting is only done few times a month. In theory, user could run the ingstart.exe program only when needed, but I'm sure that is to complicated for typical user.

iigcn and iigcc are not using CPU time, if you don't use them.
Therefore a service which is automatically started will not do much harm. I'm sure most PCs running services which are seldomly or never used.
You can also condsider starting the ODBC reporting via a batch file, which can either start the Ingres client service (using "net start <service>") or iigcn and iigcc (as mentioned before).

#2: sometimes Ingres variables get lost because of 0-byte symbol.tbl making the Ingres client unusable. OK, I must admit that problem seems to be only in old versions of the Ingres client..

I haven't seen this problem for quite some years now.

#3: Ingres client becoming unusable because client hostname is changed. Not sure, that problem may have been solved with client > 2006, haven't actually tried

You can set II_HOSTNAME to the old hostname - then the client is still usable.

#4: adding Vnodes at a later time almost anytime will fail when the user is not identical with the user that installed the client. Error message, "user does not have privileges in config.dat..."
(and yes, I *know* how to fix the config.dat in such situations and I always hate it...)

vnode definitions for remote nodes are not added to config.dat - other users should just have read permissions. It should be possible to add private vnode definitions later. In trusted environments you can also use installation passwords (so you don't have to add vnode definitions for every user).
And - as mentioned before - dynamic vnode-less connections are an alternative.

[wmSales]

Ok guys. Back to Topic please.

I cannot use the .Net Data Provider.
Reason: Microsoft Access 2003 cannot use the dll.

I'm gonna switch my tables from Ingres to SQL-Server 2008.
It seems the best solution over all.

Thanks for your help anyway.