The article "The iAnywhere JDBC Driver - Make it the First Choice" and Nick
Elson's 11/2 response re "Why two
jConnects" imply that the JDBC driver will work fine with Central. I'm
finding quite the opposite on a Standard Edition W2003 server with ASA 9.0.2
There is a MAJOR delay when logging in, and trying to view tables or
procedures. jConnect, on the other hand, is VERY speedy
Any ideas why?

What exactly are you doing?
Can you show us the connection strings you are using for both jConnect and
the iAnywhere JDBC driver?


--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/cx...c?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

"P Merritt" <pmerritt (AT) transcendonline (DOT) com> wrote

The problem first appears when I try to connect. I'm using the login screens
with Central which I imagine you know
has 3 screens.. I put username and password on the 1st screen, server name
on the second screen with Search checkbox (the iAnywhere server is running
as a service), choose either JDBC driver or jConnect 5 on the third screen..
no connection string..
should I be filling in some kind of string to log what's happening?

"Rob Waywell" <rwaywell_no_spam_please (AT) ianywhere (DOT) com> wrote

Would the fact that I created this database with version 8.0.1 and moved it
to version 9.0.2 have any effect? (I have to admit .. that would seem more
plausible to me if I were having problems with jConnect rather than the
current situation where jConnect performs so much better !)
I don't have any odbc definitions defined for this server.. and we did move
odbc registration entries from server with 8.0 to server with 9.0.2
Our ODBC driver is 9.00.02.3207

"Rob Waywell" <rwaywell_no_spam_please (AT) ianywhere (DOT) com> wrote

P Merritt wrote:
In the "Connection Parameters" box on the last tab, enter something like:

LOG=c:/asa_connection.txt

then attempt to connect with the iAnywhere JDBC driver. After you are
connected, take a look at the contents of the file c:/asa_connection.txt
to see what is going on.

The iAnywhere JDBC driver should be substantially faster than jConnect
at connecting under the vast majority of conditions (for all the reasons
outlined in the whitepaper you referenced).

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

P Merritt wrote:
I don't think that it *should*, but it might.

As I posted previously, try the LOG parameter and let's see what the
debug output in that file shows.

BTW: any particular reason that you are not unloading/reloading into a
new 9.x database file? You won't get some of the performance benefits
that come with the new file format unless you do so.

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Thanks Greg.. interestingly enough, just adding the connection parameter
made it speed up. That reminds me that we had a certicom connection
parameter on the 8.0 server but since we don't have the certicom license for
9.0.2, I'm not starting it with that parameter on 9.0.2.. bet that has
something to do with it !

"Greg Fenton" <greg.fenton_NOSPAM_ (AT) ianywhere (DOT) com> wrote

I tried it with just tcpip in the connection parameters and that speeded it
up too.. Man is THAT a relief ! thanks !
I think I just didn't bother as far at the unload and reload is concerned..
because I'm using this mostly as a gateway to remote non-Sybase servers.

"Greg Fenton" <greg.fenton_NOSPAM_ (AT) ianywhere (DOT) com> wrote

Hi

I just found the same.

Previously on Win XP Prof SP1 no problems, on SP2 and Sybase Central 4.3
*appalling* performance from the java tools (c isql and SC 4.1 fine).
Changed from JDBC to jconnect and everything fine.

I have logged a case 11193304

Justin Willey


"P Merritt" <pmerritt (AT) transcendonline (DOT) com> wrote

More on this:

Something I installed (prob SQL Server 2005 - yugh) had turned on ODBC
tracing - which is what was killing the performance. Turned that off and all
fine. (I am pretty sure that I didn't turn on tracing manually)

Justin


"Justin Willey" <gjw (AT) nospamatall (DOT) iqx.co.uk> wrote