Skip to main content

We're currently trying to convert our ISAM files to a database solution using SQL server. We've been able to succesfully connect and use SQL during our system test phase, with fewer than five users. But in the production test environment we encountered severe performance issues, as soon as at least fifteen users were using our application simultaneously.

Has anyone had similar experiences? Could there be something missing, which needs to be configured a certain way (ODBC driver, cobol code produced by Net Express, SQL Server, etc)? What about server-specific things we need to consider?

Our setup is:
Apache server, 32-bit
Net Express 5.1
Windows 2008, 64-bit
SQL Server 2008
ODBC-driver Native Client 11.0, 32-bit

Thanks for your help,

Raffi

We're currently trying to convert our ISAM files to a database solution using SQL server. We've been able to succesfully connect and use SQL during our system test phase, with fewer than five users. But in the production test environment we encountered severe performance issues, as soon as at least fifteen users were using our application simultaneously.

Has anyone had similar experiences? Could there be something missing, which needs to be configured a certain way (ODBC driver, cobol code produced by Net Express, SQL Server, etc)? What about server-specific things we need to consider?

Our setup is:
Apache server, 32-bit
Net Express 5.1
Windows 2008, 64-bit
SQL Server 2008
ODBC-driver Native Client 11.0, 32-bit

Thanks for your help,

Raffi

How is the application deployed and accessed by the users?

You have in your component list, Apache server, 32-bit.

Is this a multi-threaded web application?

Is it a mixture of COBOL and Java or pure COBOL?

Are you using a connection pool for the database connections?

Where is the database located, on the same server as the application or on a different server?

Any additional detail about your application would be appreciated...

Thanks.

We're currently trying to convert our ISAM files to a database solution using SQL server. We've been able to succesfully connect and use SQL during our system test phase, with fewer than five users. But in the production test environment we encountered severe performance issues, as soon as at least fifteen users were using our application simultaneously.

Has anyone had similar experiences? Could there be something missing, which needs to be configured a certain way (ODBC driver, cobol code produced by Net Express, SQL Server, etc)? What about server-specific things we need to consider?

Our setup is:
Apache server, 32-bit
Net Express 5.1
Windows 2008, 64-bit
SQL Server 2008
ODBC-driver Native Client 11.0, 32-bit

Thanks for your help,

Raffi

- Our COBOL executables are all single-thread.

- Our application uses COBOL, PHP and some JavaScript, and we only have experienced problems since the COBOL programs started using the SQL database.

- We aren't using a connection pool anymore, because when we used the pool the performance was even worse.

- The database is on a different server than the application

- Currently we have only four tables in the SQL database. One is read/updated on every user interaction, the other three are function dependend. PHP programs can access the SQL database without any performance issues, so we're suspecting the ODBC driver to be at fault here.

Terms & ConditionsAccessibility statement