I notice that you can only cache a DB if you open it in QA or Ent Man. if its possible I think a good option would be to manually add DB to cache. I work with servers that have over 200 db's and it would be nice to just type a few in without having to actually open QA for each.
Comments
3 comments
-
also it appears the cache deletes upon closing. Keeping the cache would also be helpful. My DB's have around 5000 tables.
Any thoughts? -
Hi,
Could you explain to me why you would want this? I don't see how caching a db without opening an editor is of any use to you.I notice that you can only cache a DB if you open it in QA or Ent Man. if its possible I think a good option would be to manually add DB to cache. I work with servers that have over 200 db's and it would be nice to just type a few in without having to actually open QA for each.
I think there is a misunderstanding here. What happens is this: When you first connect to a db, Prompt reads the schema and saves it in a file. The next time you connect to that db, Prompt reads the schema from the file (displaying a similar dialog) which should speed things up.also it appears the cache deletes upon closing. Keeping the cache would also be helpful. My DB's have around 5000 tables.
Regards,
Tilman -
Ok thanks for the clarification. The file that it reads still seems slow to me with large DB's. I guess this is the downfall of huge databases. Thanks for the reply
Add comment
Please sign in to leave a comment.