We have just completed upgradeing our main application from C9 to C11.1
We use SAP Sybase ASE SQL as our database and have for ever. The only
change is the version of Clarion. We are running exact same codeset, same
DB, same DB server. It seems that everything is slower when reading or
writing to DB.
Has anyone noticed this? Is there any changes related to SQL in the C9 vs
C11.1? Are there any changes we should/could be making to resolve this?
Clarion 11.1 Build 13855
SAP Sybase ASE version 16.0 SP03
Clarion 9.0 Build 10376
We are a call center environment so, speed is critical… Windows that
close instantly in the C9 compiled version take 3-4 seconds to close in the
C11.1 version. When the close the screen, we do the DB updates to log what
has been done etc. and I believe it is the that is taking a while. We
have also seen slowness on some management reports which are simply reading
data etc to report and these have also slowed down.
If you use Clarions driver tracing you should be able to see whats being sent to the backend and the time it takes.
You should be able to do this for both versions. You can then see if there is any difference between them in terms of SQL statements or times.
There have been changes to a few areas in SQL over the versions.
Basically what happens between your Clarion database command (SET/NEXT, PUT, ADD etc.) and getting the data back is that the Clarion “driver” turns your Clarion command into SQL, and sends it to your database’s ODBC “driver” with instructions on where to put any data it returns (a bunch of BINDs). It’s not a totally trivial thing to accomplish, but neither is it something that you would expect to see change a lot over the years.
The things that might cause your queries to get slower:
Some change in anti-virus dealing with stuff set to and from the database
Some change in what Clarion thinks the capabilities of the database are (the bad one thinking that client-side joins are the way to go)
If you have inadvertently left logging on
I’d suggest those as much more likely suspects than the change in the Clarion version.
I found the possible cause of the slowness which, if it holds true after all my testing, had nothing to do with SQL etc, it was just more evident when running queries etc.