Speed issues SQl Server 7, no primary keys

I have successfully managed to let Servoy see our accounts database systems Union Sun that is running on SQL server 7 using the Jtds jdbc driver.

It seems that SUN doesnt define the primary keys, so i have done that in Servoy as recommended.

I am not running servoy on the same machine as the SQL Server.

The speed seems terribly slow compared to using MSQuery over ODBC.

Is this because Servoy is have to create its own primary keys or is it because servoy is not on the machine local to the Sqlserver?

Any tips

David

I think it is difficult to answer just like that.

It could be the setup local/remote. The last will always be slower but how much depends on wether local/internet etc.

It could be your driver. Is it the latest available for instance.

Another thing, is it really the setup or just the things you let Servoy do that slow things down (not the pk, that can’t be it imho).

Thanks Marcel,

It is interesting.

I have used a global variable of the Account_code, which is the row_ident i have put on the sales ledger table. That makes it a lot quicker rather bringing up an individual record from the Accounts table and linking from the selected record.

It is a little weird because it then seem to show multiple entries from the salesledger table repeating them many time instead of listing each one. Its almost like it create the wrong type of join.

I think i need to speak to SUN accounts to understand why their database doesnt have primary keys on it. Funny thing is it works fine in MS Query.