If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > probelm in retrieving data in powerbuilder when connecting to db2/400 through ODBC

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-20-05, 03:55
deyaa_tahhan deyaa_tahhan is offline
Registered User
 
Join Date: Sep 2005
Posts: 2
Question probelm in retrieving data in powerbuilder when connecting to db2/400 through ODBC

I have a problem while retrieving data from powerbuilder ISQL when connecting to db2/400 through ODBC connection.
The problem is the large consumed time when retrieving data from any table specially when the table has alot of columns
(e.g. Retrieving from table that has 100 columns and 17000 records cost me exactly 2 minutes)
Is there any pre-configurations in db2/400, ODBC, or powerbuilder to improve this performance????????
Please send me all the possible causes and possible solutions.
please contact me ASAP.
Thanks for consideration.
Reply With Quote
  #2 (permalink)  
Old 09-20-05, 09:07
Wim Wim is offline
Registered User
 
Join Date: Nov 2004
Posts: 1,279
What version of PowerBuilder do you use ?

What is your DbParm (ConnectString) to your database ?

If you access the database from another application via ODBC (eg MS Access), do you get the same performance ?

Is the version of the client (ODBC) the same as on the server ?
__________________
With kind regards . . . . . SQL Server 2000/2005/2008/2008 R2 Earned beers: 16
Wim
Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth
Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages
Reply With Quote
  #3 (permalink)  
Old 09-20-05, 11:27
deyaa_tahhan deyaa_tahhan is offline
Registered User
 
Join Date: Sep 2005
Posts: 2
Question

1 - Version : PowerBuilder7 with last updates
2 - Connection String :
// Profile eastern_db
SQLCA.DBMS = "ODBC"
SQLCA.AutoCommit = False
SQLCA.DBParm = "ConnectString='DSN=eastern_db;UID=rada;PWD=ra da'"

3 - The Performance when using access is very different from powerbuilder
as you see in the sent example, when using MS Access the time is only
1 (only one ) second.But when using VB it spent time about 2 minutes.

4 - The version of ODBC is the same on both client and server Client Access5

Please Notice:
1 - I have tried to use another versions of powerbuilder but the result is still
the same.
2 - I have tried to change on some of the ODBC DSN options but the result
also still the same.
3 - The ODBC DSN options that I tried to change are : -
* Enable or Disable Pattern Search CheckBox
* Enable or Disable Extended Dynamic (Packages) Support.
* Change The Record Blocking Size.
* Enable OR Disable DataCompression.
4 - I have read alot of documents that help in improving performance but
there is no actual improvement.
5 - There is no differenece in consumed time when running a SQL statement
from PowerBuilder ISQL or from retrieveng through DW in RunTime.
6 - Some times The performance when using VB is worse than using
PowerBuilder.
7 - The client configuration is very perfect with large Physical memory size.
undefined
Reply With Quote
  #4 (permalink)  
Old 09-21-05, 03:01
Wim Wim is offline
Registered User
 
Join Date: Nov 2004
Posts: 1,279
My DBPARM would look something like:

DBParm = "ConnectString='DSN=eastern_db;UID=rada;PWD=rada', IdentifierQuoteChar='"',DelimitIdentifier='No'"

I don't expect the difference to affect the performance.

You could contact Sybase.
__________________
With kind regards . . . . . SQL Server 2000/2005/2008/2008 R2 Earned beers: 16
Wim
Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth
Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On