SAPIEN Forums

When starting PrimalSQL 2009, it takes up to 15 minutes for the program to load.

I am logging in remotely via citrix, and I have active connections established.

Are you opening a query file or just running PrimalSQL from a shortcut? In addition, what OS are you running?


Thank you,

David

I am running Windows Server 2003 R2, 64 bit, sp2

Now I have only one db connection, and it is taking a very long time to return results from a query.

Is the database on the same machine? What provider are you using?
If there is a slow connection, it can take some time for the query builder to build the internal metadata. Try using the SQL Text Document to run your query and see if it makes a difference. In addition, running queries in ReadOnly mode will help speed up the query results.

David

The db is not on the same machine; but it is on SAN connected with Fiberchannel. There is 1gigabit between servers. I am running the query within the same context.

We are querying several thousand rows within the db. Can PrimalSQL handle that kind of throughput?

I do not believe we have a bandwidth or connectivity problem.

It should be able to handle large amount of rows, but it can also depend on the context of the rows, indexing in the database, or connection type. Is AppData folder mapped to a network location?

yes

That could be the source of the slow down. It uses the AppData folder as a data cache.

what is the default path to the appdata folder?

I'm not sure what the path is for Windows Server 2003, but here the paths for the other Windows versions:

Windows 7:
C:Users<username>AppDataRoaming



Windows XP:
C:Documents and Settings<username>Application Data