|
All, I have a JDBC based application that is extracting data from an iSeries database, and writing it out to an MS SQL Server database. In eclipse on my PC a simple extract takes about 5 secs. However when I move the code onto the iSeries, the same extract takes 55 secs, a 10 fold increase. Changing the iSeries database driver from jt400 to db2 makes no difference. Running crtjvapgm on all the jar's makes no difference. Looking at my log output, most of the time is spent creating the SQL server connection. Why would this take so long on the iSeries, but be practically instantaneous on my PC? (The SQL server database is not local to my PC either, it's on the other side of a firewall). I'm using the MS sqljdbc.jar I downloaded from the MS website. Are there some tuning options I can play with? Is there a better jar to use? Anyone else had this problem? Regards, Chris. ****************************************************** The information in this E-mail and in any attachment is confidential and is intended solely for the addressee. Access, copying, disclosure or use of such information by anyone else is unauthorised. If you are not the intended recipient please contact postmaster@xxxxxxxxxxxxxx While reasonable efforts are made to ensure these files are free of virus infection and offensive materials, if something of this nature is inadvertently sent to you, please destroy it, accept our apologies and contact postmaster@xxxxxxxxxxxxx with details of the sender. We will ensure that action is taken immediately to prevent any recurrence. Debenhams accept no responsibility for any views expressed by the originator of this email. Debenhams Retail plc (reg. no. 83395) Registered in England and Wales. Registered office: 1 Welbeck Street, London W1G 0AA. http://www.debenhams.com ******************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.