Comments
Sort by recent activity
Great, glad that sorted it. I did wonder if your INSERT was a stylised representation. [image] / comments
Great, glad that sorted it. I did wonder if your INSERT was a stylised representation.
OK, that's a very odd INSERT statement... but that aside, if your statements are typically long you may run into SQL Prompt's hard limit for the amount of SQL it will parse, and this can lead to you getting no useful auto-complete suggestions. I say "hard" in the sense that SQL Prompt won't go beyond it, however you can change the value.
1) Open the Options dialog by clicking SQL Prompt > Options on the main menu.
2) Go to the Listed Candidates > Variables and Parameters screen. Now either (a) increase the maximum number of lines, or (b) select "Search entire batch/GO block..."
Then you're good to go. Note that if you work with large scripts with very large SQL batches going for option (b) above may well degrade performance. I'd suggest (a) and in the initial case increase the value to 100 or 150.
Hope that helps.
Thanks,
Bart / comments
OK, that's a very odd INSERT statement... but that aside, if your statements are typically long you may run into SQL Prompt's hard limit for the amount of SQL it will parse, and this can lead to yo...
No problem. I'm just glad we finally found it: Jason finally managed to isolate it a couple of days ago. / comments
No problem. I'm just glad we finally found it: Jason finally managed to isolate it a couple of days ago.
Hi there,
As documented in the online help SQL Prompt may not provide correct auto-complete suggestions where syntax errors exist in your SQL. "SELECT FROM" is one such error. The best thing to do is make sure you always start your queries with "SELECT * FROM" and specify the column list, either manually or using the column picker, once you've completed the FROM clause.
There is an ssf snippet that will insert "SELECT * FROM" quickly, and you can obviously edit this if you want to break it onto more than one line. You'll find the snippet editor in the Options dialog under SQL Prompt > Options from your editor's main menu bar.
Hope that helps.
Thanks,
Bart / comments
Hi there,
As documented in the online help SQL Prompt may not provide correct auto-complete suggestions where syntax errors exist in your SQL. "SELECT FROM" is one such error. The best thing to do ...
Hi Robin,
Thanks for reporting this. It's been filed as a bug and fixed this morning. It'll be available in the 3.6 final release, which we're now thinking will be out early-mid next week. We've made a couple of other fixes as well so we need some additional test time.
Cheers,
Bart / comments
Hi Robin,
Thanks for reporting this. It's been filed as a bug and fixed this morning. It'll be available in the 3.6 final release, which we're now thinking will be out early-mid next week. We've ma...
Hi there,
If you've previously installed a 3.x version of SQL Prompt for evaluation you'll probably, although I'm not 100% certain about this, need a trial license (free) in order to evaluate 3.6. Please contact sales@red-gate.com who will be able to provide you with the information you need.
Thanks,
Bart / comments
Hi there,
If you've previously installed a 3.x version of SQL Prompt for evaluation you'll probably, although I'm not 100% certain about this, need a trial license (free) in order to evaluate 3.6. ...
Hi Pete,
Unfortunately we don't yet offer that functionality and I can't tell you when it might become available: it certainly won't be part of the 3.6 release that's coming out later this week.
Sorry I can't be more help right now.
Thanks,
Bart / comments
Hi Pete,
Unfortunately we don't yet offer that functionality and I can't tell you when it might become available: it certainly won't be part of the 3.6 release that's coming out later this week.
So...
Great, glad that fixed in for you Scott. I'm hoping to get an RC out tomorrow, probably fairly late in the day UK time so I'd suggest downloading that and giving it a try with the cross-database support enabled. Hopefully this will fix the problem, but if not we'll try something else since we don't want to let another release out that suffers from the issue.
Watch this space.
Cheers,
Bart / comments
Great, glad that fixed in for you Scott. I'm hoping to get an RC out tomorrow, probably fairly late in the day UK time so I'd suggest downloading that and giving it a try with the cross-database su...
Hi Scott,
Sorry to see you're having problems. You haven't given me much to go on but if this: http://www.red-gate.com/MessageBoard/vi ... php?t=5457
is the kind of thing you're seeing then the workaround for now is to disable cross-database support.
We'll have a release out that fixes this problem within the next week or two.
You may also wish to check out the troubleshooting and tips sections in the web help, accessible via the SQL Prompt menu, which provide additional information on tuning the performance of Prompt.
Hope that helps.
Thanks,
Bart / comments
Hi Scott,
Sorry to see you're having problems. You haven't given me much to go on but if this:http://www.red-gate.com/MessageBoard/vi ... php?t=5457
is the kind of thing you're seeing then the work...
Finally we've managed to reproduce this problem, and I've put in a fix for it this morning which will be available in the 3.6 release. We're planning to get that out later this week. I'll make an announcement on the forums when it becomes available. Note that this problem isn't fixed in the 3.6 EA release that's currently available.
Hope that helps.
Thanks,
Bart / comments
Finally we've managed to reproduce this problem, and I've put in a fix for it this morning which will be available in the 3.6 release. We're planning to get that out later this week. I'll make an a...