Comments
Sort by recent activity
Hi Matt,
Thanks for your bug report. I can confirm I've reproduced your issue, and that neither the Refresh button, the Refresh Suggestions option nor closing and opening SSMS makes the correct script appear for myNewTestProc.
The issue is logged as SP-2927 in our internal bug-tracking system.
If the SP is redefined as ALTER PROCEDURE dbo.myNewTestProc ... then the Script as ALTER button works again. Also, note that if you use SQL Prompt 5's Smart Rename feature to rename the procedure then this issue does not arise.
Regards,
Paul / comments
Hi Matt,
Thanks for your bug report. I can confirm I've reproduced your issue, and that neither the Refresh button, the Refresh Suggestions option nor closing and opening SSMS makes the correct sc...
Hi rcampbellwhite,
Yes, I'm pleased to say that SP-4009 was fixed in SQL Prompt 5.1.8 and is now available. Please see my announcement.
Regards,
Paul / comments
Hi rcampbellwhite,
Yes, I'm pleased to say that SP-4009 was fixed in SQL Prompt 5.1.8 and is now available. Please see my announcement.
Regards,
Paul
Hi Bill,
Thanks for the report about Visual Studio crashing when adding a snippet. I can confirm that this is an issue with SQL Prompt 5.1.6 when running inside Visual Studio (it doesn't happen on SSMS). This has been assigned issue number SP-4009 and we'll address it in the next bug-fix release.
Apologies for the inconvenience.
Regards,
Paul / comments
Hi Bill,
Thanks for the report about Visual Studio crashing when adding a snippet. I can confirm that this is an issue with SQL Prompt 5.1.6 when running inside Visual Studio (it doesn't happen on...
Thanks for the BIDS workaround, and for confirming that SQL Prompt 5 still works in SSMS afterwards!
Regards,
Paul / comments
Thanks for the BIDS workaround, and for confirming that SQL Prompt 5 still works in SSMS afterwards!
Regards,
Paul
Thanks for the workaround! As someone mentioned in another thread, if you uncheck SQL Prompt 5 in BIDS, it does still work in SSMS.
Regards,
Paul / comments
Thanks for the workaround! As someone mentioned in another thread, if you uncheck SQL Prompt 5 in BIDS, it does still work in SSMS.
Regards,
Paul
Hi Mike,
I've just tried typing ssf with various completion keys in SQL Prompt 4 and SQL Prompt 5, and I haven't yet see any differences in behaviour. You're correct that after completing the ssf snippet, you have to type ctrl-space to show the list of tables.
If you've managed to get the list of tables to appear immediately after completing the snippet, could you let me know which completion keys you have set up, and what keystrokes you are using?
Thanks,
Paul / comments
Hi Mike,
I've just tried typing ssf with various completion keys in SQL Prompt 4 and SQL Prompt 5, and I haven't yet see any differences in behaviour. You're correct that after completing the ssf ...
Hi Jack,
With your help, I've traced this to a change in SQL Prompt 3.8 that stopped regarding INNER JOIN as a Boolean operator, because it affected other formatting operations.
This means that SQL Prompt does not allow use of the "Start new line at Boolean operator > Place operator at end" option to control where INNER JOIN goes.
If others are missing this functionality then please post here, as we're more likely to address it if lots of users want this changed.
Regards,
Paul / comments
Hi Jack,
With your help, I've traced this to a change in SQL Prompt 3.8 that stopped regarding INNER JOIN as a Boolean operator, because it affected other formatting operations.
This means that SQL...
The slowness is down to the SQL Prompt parser working extremely hard. In this case it seems that having many columns and table-like objects (temporary tables and CTEs) that are themselves embedded SELECT statements seem to be killing it. It's not going into an infinite loop, but enough things trigger another pass through the script that the parser starts again as soon as it finishes, causing SSMS to become unresponsive.
There are some possibilities around avoiding too many repeat parses, but no easy solution has so far presented itself, I'm afraid. The parsing code is very complex, but we hope to be able to make some improvements in a future release without breaking any other behaviour. / comments
The slowness is down to the SQL Prompt parser working extremely hard. In this case it seems that having many columns and table-like objects (temporary tables and CTEs) that are themselves embedded...
Here at Red Gate the developers have identified that there was a gross inefficiency in the way scripts with CTEs were parsed. This has now been resolved and the fix will be included in SQL Prompt 5.1.
As this is a serious error, we've backported the fix to 5.0, but haven't fully regression-tested it. I've emailed people on this thread with a link to the private download. If others reading this are suffering from slow performance with CTEs and would like to try the patched version, then please email me at paul.stephenson@red-gate.com.
Regards,
Paul / comments
Here at Red Gate the developers have identified that there was a gross inefficiency in the way scripts with CTEs were parsed. This has now been resolved and the fix will be included in SQL Prompt ...
As an update to my previous post, please be aware that the CTE slowdown fix is one of the improvements in the 5.1 beta release, so if you are experiencing this issue then download from the link in the 5.1 beta announcement.
Regards,
Paul / comments
As an update to my previous post, please be aware that the CTE slowdown fix is one of the improvements in the 5.1 beta release, so if you are experiencing this issue then download from the link in ...