I thought I'd add my feedback here since my biggest complaint echoes what was said above.
I've found that the current behavior of the program doesn't feel intuitive while typing. Especially since it seems to depart in many ways from the behavior of SQL Prompt 2 (A problem for anybody who is upgrading) I've found that it has drifted away from, rather than closer to, the behavior of Visual Studio. SQL Prompt 2 provided better emulation in my opinion.
I installed the latest patch version, and within an hour have uninstalled it because it was more frustrating to use than it was helpful. I was spending more time trying to figure out how to make the program make my queries easier to write than it would have taken to write the queries from scratch.
The menu rarely seemed to trigger when I would expect it to
The options in the menu were often inappropriate (As mentioned in previous posts, column names where only table names should be, etc)
I ended up reinstalling SQL Prompt 2, it seems to meet my personal feel for contextual help better than the new version. Perhaps an option could be added to allow the user to change the behavior of the menu? {Completely Passive (User must trigger menu manually) ... Current Version of SQL Prompt 3 ... More Aggressive [SQL PRompt 2] ... Most aggressive (if possible?)} - you can't make everybody happy, so you may as well give them the option to make themselves happy.
Other things:
I'd like to suggest is that you include the ability to access the SQL Prompt options from the system tray as was done in SQL Prompt 2. That is the first place I looked for it, I didn't even notice the added menu in QA until I consulted the help file to see where the options were. (The default exclusion of tab as a completion character was really killing my typing)
There are options for forcing keywords / functions / etc to be all UPPER / lower / [user's original], but you may want to add PascalCase (TitleCase ?) as an option in case there are people who'd like something in-between
I liked the improved notification of when it is generating schema information
The popup seemed to have some nice ideas for useability, such as showing the characters you'd typed and the grouping of selections, etc.
Best of luck with the development, I've found your database comparison products very helpful and hope that SQL Prompt 3 winds up to be equally helpful. / comments
- Community
- SQL Prompt 3
- No CL for simple situation - Build 819
I thought I'd add my feedback here since my biggest complaint echoes what was said above.
I've found that the current behavior of the program doesn't feel intuitive while typing. Especially since i...
0 votes
