Comments
6 comments
-
Yes, I agree completely. Sometimes it works and sometimes it doesn't. I use Query Analyzer 8.00 and it appears to work intermittently. For example, when I type 'select * from ' it should pop up a list of tables in the current database. I have tried different combinations of options and no luck! What's up with it?
-
I couldn't have said it better myself!
-
I have scruples in "to buy or not to buy" it because of this kind of malfunction of this really usefull tool. I suggest that it would be better to postpone the V3 release and fix this kind of annoyng bugs in V2. This way you'll get more admires, supporters and potential buyers.
Best Regards.
8) -
Hi there,
I'm sorry I haven't managed to get around to responding to your comments before, but we are grateful for the feedback and I think you make some very fair points about SQL Prompt 2.
It does work very intermittently and unfortunately there's not really one single reason why it does this: the product has many problems and in the end that's why we decided to give it away for free rather than sell it. We just didn't think we could make it live up to the same pedigree as the rest of our toolset for version 2. You do have to remember though that it was largely written by one guy in his spare time on the train commuting to and from his day job, and on that basis I think it's a pretty impressive achievement.
We bought it obviously with a view to fixing a few bugs and then releasing and selling it as a Red Gate product. However it became apparent that as time went on this wasn't really going to work, and that due to the complexity of the SQL intellisense problem there were some very fundamental issues with the SQL Prompt 2 that were going to take a lot more than a few simple bug fixes to sort out. As identified on this thread:
http://forums.microsoft.com/MSDN/ShowPo ... 1&PageID=0
on the Microsoft forums getting "something" working isn't really the problem; getting it working right is.
We've spent the past nearly 6 months trying to do just that, and it's turned out to be harder than even we suspected after our experiences with SQL Prompt 2. From a commercial perspective putting in this amount of effort on SQL Prompt 2 simply isn't a viable option because it's a free tool and will be freely available for download from our website (http://www.red-gate.com/products/SQL_Prompt/index.htm) until the release of version 3.
As with most of our other tools, SQL Prompt 3 will offer a 14-day fully functional trial during for evaluation purposes. However, if you wish to take advantage of the $99 pre-order offer you can still do so as this applies until the release of the new version. If having done this you are dissatisfied with version 3 we will of course be more than happy to offer you a full refund. Additionally a release candidate will be available in the next few weeks so you can still try before you buy even where the special order is concerned.
Many thanks,
Bart -
One reason that it can appear to work intermittently is that version 2 only looks at the text before and after the cursor that is delimited by blank lines ... so ensure that your current SELECT has a blank line before it...
-
That's quite true. You also need to ensure that your SELECT statement doesn't have any blank lines within it because version 2 tends to get spoofed by whitespace pretty easily.
Add comment
Please sign in to leave a comment.
Windows XP, SP2. Using SQL Server QA 8.00.194. Multiple people's machines. The problem we have is that sometimes it'll work, sometimes it won't. I can be typing out code, get to the next line, and suddenly hitting [TAB][TAB] will pop up and insert the first column of the table I'm working on. Next line, that won't happen (which is nice, since I normally indent code), and it didn't happen in the previous line. Sometimes hitting CTRL+SPACE will complete the snippet I just typed , other times I can hit it 20 times and nothing happens. Sometimes it will bring up columns I need in the WHERE field, and sometimes it won't.
I can't see any rhyme or reason to it. Is there some way to make sure it will work? Are there some "best practices" to make sure it comes up as much as possible? We've already had a couple people abandon it due to this, and I'm about to.
Please don't say "it'll be fixed in version 3". Yes, I know you're rewriting it. However, it has to come out first, then we have to decide if this one is going to be worth the effort, and if so then I have to get approval, so it may be a while. Having it work now would make it easier to justify, rather than saying "that tool we bought licenses for? We need to buy a more expensive license for the same tool so that it works"
I know this message sounds exceeding hateful - it's not. We're just extremely frustrated with a tool with so much promise, that only works when it decides it's in the mood.