How to conect ingres with Java in windows XP

Hello, I want to use Java to perform queries in my ingres database. Currently
there is an ODBC driver installed in the server but I would like to use JDBC
driver to connect directly with the database without using a JDBC/ODBC bridge.


Please can somebody tell me what do I need to install and how? Also would you
know if this drivers are available for free which I am interested in?

Many thanks
Nikolla

"koli1980" wrote in message news:85f1fa2744ec6-at-uwe...
> Hello, I want to use Java to perform queries in my ingres database.
> Currently
> there is an ODBC driver installed in the server but I would like to use
> JDBC
> driver to connect directly with the database without using a JDBC/ODBC
> bridge.
>
>
> Please can somebody tell me what do I need to install and how? Also would
> you
> know if this drivers are available for free which I am interested in?

JDBC support is included with when you install Ingres 2006. Just make sure
you have a Data Access Server configured to start, although it probably
starts automatically.

Take a look at
http://docs.ingres.com/connectivity/...BCConnectivity.

Roy

Greetings oh Ingres Gurus


Is it possible for a .net application to connect to an ingres database where
the server is Ingres II 2.6 sp5.

If it is, what would the application server have to have installed (if
anything) to allow this to happen.

Yes, he could use ingres net and odbc, but what he really wants to use is an
ingres .net data provider.....

is this possible??



Cheers

Richard

/**********************************\
| New Zealander, leading the world |
\**********************************/

2008/6/20 Richard Harden :

> Greetings oh Ingres Gurus
>
>
> Is it possible for a .net application to connect to an ingres database
> where the server is Ingres II 2.6 sp5.
>
> If it is, what would the application server have to have installed (if
> anything) to allow this to happen.
>
> Yes, he could use ingres net and odbc, but what he really wants to use is
> an ingres .net data provider.....
>
> is this possible??
>
>
> Cheers
>
> *Richard*
>

Richard,

Hi. The .Net data provider requires the Data Access Server to connect to and
that's not available in 2.6. However what you could do is set up an Ingres
2006 installation, with DAS, create a vnode from it to the 2.6 installation
and then use vnode::dbname instead of dbname in your .Net connection. If I
was doing something like this I'd put the 2006 install on the same machine
as the existing 2.6 install, which should reduce any Ingres Net overhead
(probably minor anyway) and use it as part of a phased approach to upgrading
to 2006 anyway.

HTH



--
Paul Mason

Thanks Paul,

I'll give it a go




Cheers

Richard

/**********************************\
| New Zealander, leading the world |
\**********************************/



_____

From: info-ingres-bounces-at-kettleriverconsulting.com
[mailto:info-ingres-bounces-at-kettleriverconsulting.com] On Behalf Of Paul
Mason
Sent: Saturday, 21 June 2008 1:13 a.m.
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Ingres .NET data provider




2008/6/20 Richard Harden :


Greetings oh Ingres Gurus


Is it possible for a .net application to connect to an ingres database where
the server is Ingres II 2.6 sp5.

If it is, what would the application server have to have installed (if
anything) to allow this to happen.

Yes, he could use ingres net and odbc, but what he really wants to use is an
ingres .net data provider.....

is this possible??



Cheers

Richard


Richard,

Hi. The .Net data provider requires the Data Access Server to connect to and
that's not available in 2.6. However what you could do is set up an Ingres
2006 installation, with DAS, create a vnode from it to the 2.6 installation
and then use vnode::dbname instead of dbname in your .Net connection. If I
was doing something like this I'd put the 2006 install on the same machine
as the existing 2.6 install, which should reduce any Ingres Net overhead
(probably minor anyway) and use it as part of a phased approach to upgrading
to 2006 anyway.

HTH




--
Paul Mason