Marc,
Do you know if using the Sprinta2000 driver with Orion provides
connnection pooling? According to Inet-soft, their Opta driver
is the one that provides connection pooling, not the Sprinta driver.
But Orion also implements connection pooling, so which driver is
really needed?
What would happen if you used a driver that did connection pooling,
like the Opta driver, along with Orion?
-gary
--- Marc Russell <[EMAIL PROTECTED]> wrote:
> Michael,
>
> I'll cheerfully volunteer that the JDBC-ODBC bridge driver is
> slooooow. We
> are using the Sprinta2000 driver, which is a commercial
> implementation of
> Microsoft's TDS protocol, and it seems to function quite well. To
> use that
> driver, the data-sources.xml file looks like this (after, of course,
> you buy
> the driver):
>
> <data-source
> class="com.evermind.sql.DriverManagerDataSource"
> name="ecr"
> schema="database-schemas/ms-sql.xml"
> location="jdbc/ecrCoreDS"
> xa-location="jdbc/xa/ecrXADS"
> ejb-location="jdbc/ecrDS"
> connection-driver="com.inet.tds.TdsDriver"
> username="USER"
> password="PASSWORD"
> url="jdbc:inetdae7:SERVER:1433?database=DB"
> inactivity-timeout="30"
> />
>
> Replace USER with the username, PASSWORD with the password, SERVER
> with the
> IP address or DNS for the server and DB with the name of the
> database. And
> yes, this is running over TCP/IP, so your SQL Server needs to be
> listening
> on port 1433.
>
> You can buy the Sprinta2000 driver at
> http://www.inetsoftware.de/English/Produkte/JDBC_Overview/default.htm
>
> If you instead decide to go for the straight up JDBC-ODBC bridge, the
> data-sources entry is like this:
>
> <data-source
> class="com.evermind.sql.DriverManagerDataSource"
> name="SQLServer"
> schema="database-schemas/ms-sql.xml"
> location="jdbc/SQLServerCoreDS"
> xa-location="jdbc/xa/SQLServerXADS"
> ejb-location="jdbc/SQLServerDS"
> connection-driver="sun.jdbc.odbc.JdbcOdbcDriver"
> username=USERNAME"
> password="PASSWORD"
> url="jdbc:odbc:DATASOURCE"
> inactivity-timeout="30"
> />
>
> In this case, DATASOURCE is replaced by the name of a System ODBC
> datasource
> defined on the Windows host that points to the SQL Server. This
> allows the
> SQL Server to listen just on named pipes, and provides a certain
> level of
> indirection to prying eyes, but our experience was that it did not
> perform
> very well.
>
> Regards,
>
> Marc Russell
> Exem Company
>
> > -----Original Message-----
> > From: Michael S. Kelly [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 21, 2000 2:21 PM
> > To: Orion-Interest
> > Subject: Orion, JDBC-ODBC bridge, and SQL Server
> >
> >
> > Anyone out there that is using the the JDBC-ODBC bridge that
> > would share
> > their data-sources.xml file with me? I plan on using SQL Server
> 2000.
> > Anything special I should know?
> >
> > -=michael=-
> >
> >
>
======================================================================
> > Michael S. Kelly ____ _
> > Axian, Inc. // |_ __(_) ___ _ __
> > 4800 SW Griffith Dr., Ste. 202 //| |\\/ /| |/ _ \| '_
> \
> > Beaverton, OR 97005 USA _____//_| | / / | | |_| | | |
> |
> > Voice: (503)644-6106 x122 (( // |_|/_/\\|_|\_/|_|_|
> |_|
> > Fax: (503)643-8425 ``-'' ``-''
> > http://www2.axian.com Software Consulting and
> Training
> > mailto:[EMAIL PROTECTED]
> >
>
======================================================================
> >
> >
> >
>
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
