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.
PrimalSQL is very slow to start
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
PrimalSQL is very slow to start
Are you opening a query file or just running PrimalSQL from a shortcut? In addition, what OS are you running?
Thank you,
David
Thank you,
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- tfranciosi
- Posts: 5
- Last visit: Mon Feb 28, 2011 9:46 pm
PrimalSQL is very slow to start
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.
Now I have only one db connection, and it is taking a very long time to return results from a query.
PrimalSQL is very slow to start
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
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
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- tfranciosi
- Posts: 5
- Last visit: Mon Feb 28, 2011 9:46 pm
PrimalSQL is very slow to start
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.
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.
PrimalSQL is very slow to start
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?
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
PrimalSQL is very slow to start
That could be the source of the slow down. It uses the AppData folder as a data cache.
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- tfranciosi
- Posts: 5
- Last visit: Mon Feb 28, 2011 9:46 pm
PrimalSQL is very slow to start
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
Windows 7:
C:Users<username>AppDataRoaming
Windows XP:
C:Documents and Settings<username>Application Data
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.