Test test test is right Wayne.
I installed the freely distributed version 1.0 of SQLPrompt on my machine, and it ran away with all the system resources, taking 99% of the CPU utilization. I had to deinstall it again, much as I liked the functionality, I couldn't accept the impact it was having on the performance of my machine...
David
My company bought a license from the guy that did this before Red-Gate bought it. I was please with the last version 1.4 before it was sold. It did take some resources. I switched back from 2.0 to 1.4. Hopefully our licenses will be retroactive.
I'm having similiar slowness problems. When it is searching the database for a list of fields or tables to show, my cpu is tagged and it acutally slows me down instead of speeding me up. I typically have to wait 2-5 seconds before my cursor will move again. In that time I could have just typed it out. Also I find if I am not looking at the screen and just typing away, prompt may have put up its pop-up, slowed my system down and I chose something from the list instead of doing what I was typing.
Neat idea, but it appears to slow me down more than help.
Thanks Red Gate - hopefully the next version will get the lead out.
I just downloaded the newest version (2.0.0.0) and was happy until I read the comment from bnordberg about typing with their head down.
If I type in:
"select * from " and let the application list the tables to choose from, and select a table (Agency), it displays:
"select * from Agency", which is fine. And if I then add "where ", it pops up a list of field names, which is also fine.
However, if I am typing away and type in:
"select * from agency where ", the intellisense program lists all of the functions, none of the fields for the table "Agency". It is as if it is case sensitive. If i go back and replace the "a" with "A", it shows the table fields.
Guess I'll have to experiment with it. I love the concept, because I'm sort of a newbie to a lot of the sql syntax, and some of the tables I work with were not quite consistent with their field naming conventions (agencyid, agencycode, agencynumber may all refer to same data in different tables...).
Thanks
Steve
I have been using SQLPrompt for a while and still like it. It doesn't always work but I've learnt to work around it. The slowness is usually just when you open up a new connection. INSERT statements seem to produce a list of tables rather than columns of the table you are writing the statement for. I also get times when it just stops giving me options completely.
I wouldn't write it off completely though. It's a great idea and some features are really useful. If Red Gate can iron out the bugs it'll be worth paying for IMHO.
