For reporting purposes, I have created a separate Sybase 10 dbspace ‘stb_view’ on the same database server as where servoy is running at the dbspace ‘stb_relation’. I want to make some tables of the ‘stb_relation’ dbspace accessible via a remote server which I created using Sybase Central. Its connection type is SQL Anywhere and the connection url looks like this: localhost:2610/stb_relation.
When I create a proxy table on let’s say table organisation and query it using ‘select * from organisation’ it takes about 3 minutes to get all 1200 records and 20 columns. I can’t imagine this is a plausible speed, but i I think you’ll agree it wil take a really long (unacceptible) time on more than 1 million records (which is the case for our customer). Am I doing something wrong here or is there a better solution to achieve this?
I’m not sure what connection you mean. Both dbspaces are on the same physical machine on the same sybase database instance. Or are you suggesting that the db connection should look different from ‘localhost:2610/stb_relation’?
What I mean is that you are talking about a remote connection that you (want to) make.
So what I was trying to ask is: are you sure that it is not the remote connection that slows things down due to firewall etc. issues…
I just called it a remote connection because Sybase calls it that. It is a remote server as can be setup using Sybase Central. This just links to another dbspace on the very same server. This is because it is not possible in Sybase to query one database from another.