Hi all
I have an application that reads and writes when producing a report for +-200 clients monthly data. The reading is done to collect data and the writing is done to store data in a self made temp. table for later use. This process happens 1 per client that the report is used for. The reading is fine but the writing to the table times out and stop the report from running. On win 98 I don't have a problem, on Win 2000 it takes 45 seconds (everytime) before I get the time out and on Win XP it takes 15 seconds (everytime) to timeout. These timeout values stays the same everytime I run this big report. If I use 50 clients the report takes +- 2 min to run but completes on all client OSes.
I'm thinking that I have problems with a write buffer becoming full and the server is trying to flush the buffer but can't. Is this possible or what else can be wrong.
Server
Server: 3.23.48 max (tried v4.x and v5.0 same problem)
Memory: 4 Gig
CPU: P4 2.8 Intel
OS: Suse LINUX
Client ODBC Driver: 3.51.14 (happens on all ODBC drivers after 3.51.06
Thank you for your help
Andrew
I have an application that reads and writes when producing a report for +-200 clients monthly data. The reading is done to collect data and the writing is done to store data in a self made temp. table for later use. This process happens 1 per client that the report is used for. The reading is fine but the writing to the table times out and stop the report from running. On win 98 I don't have a problem, on Win 2000 it takes 45 seconds (everytime) before I get the time out and on Win XP it takes 15 seconds (everytime) to timeout. These timeout values stays the same everytime I run this big report. If I use 50 clients the report takes +- 2 min to run but completes on all client OSes.
I'm thinking that I have problems with a write buffer becoming full and the server is trying to flush the buffer but can't. Is this possible or what else can be wrong.
Server
Server: 3.23.48 max (tried v4.x and v5.0 same problem)
Memory: 4 Gig
CPU: P4 2.8 Intel
OS: Suse LINUX
Client ODBC Driver: 3.51.14 (happens on all ODBC drivers after 3.51.06
Thank you for your help
Andrew
Comment