Comments
Sort by recent activity
Hi,
We have identified the performance issue with expanding Object Explorer nodes (eg Tables) in versions 3.6.6 and 3.6.7 of SQL Source Control. A database request is unnecessarily made for every object in the list, so the performance hit will depend on the speed of connections to your SQL Server instance.
A fix is in the pipeline, and we hope to make it available this week to frequent updates. / comments
Hi,
We have identified the performance issue with expanding Object Explorer nodes (eg Tables) in versions 3.6.6 and 3.6.7 of SQL Source Control. A database request is unnecessarily made for every ...
Hi Danny,
Since Thursday 7th there has been a new build of SQL Tab Magic available for download. This is functionally identical to the previous build but no longer has any expiration date.
If this doesn't work, please let us know! / comments
Hi Danny,
Since Thursday 7th there has been a new build of SQL Tab Magic available for download. This is functionally identical to the previous build but no longer has any expiration date.
If this...
Hi bkolundzic,
I'm afraid SQL Prompt doesn't currently identify the connection automatically for Visual Studio query windows.
Please add your vote to this feature suggestion to improve its chances of being selected when SQL Prompt development work is next prioritised. / comments
Hi bkolundzic,
I'm afraid SQL Prompt doesn't currently identify the connection automatically for Visual Studio query windows.
Please add your vote to this feature suggestion to improve its chances ...
Hi Jeff,
We believe this issue is fixed in SQL Prompt 5.3.4. You should be able to update your copy to this version by going to SQL Prompt 5 > Help > Check for Updates....
Please reply here whether it worked for you or not!
Regards,
Paul / comments
Hi Jeff,
We believe this issue is fixed in SQL Prompt 5.3.4. You should be able to update your copy to this version by going to SQL Prompt 5 > Help > Check for Updates....
Please reply here whethe...
Thanks for the feedback Jeff. It's good to see that you've got SQL Prompt working in your environment now.
SQL Prompt in Visual Studio sometimes has problems automatically identifying the database connection when you're editing a query, which is why the Connect to Server... option is there to do it manually. This is not needed in SQL Server Management Studio as the connection is always identified.
You say you "recently installed Visual Studio 2010": have you used SQL Prompt inside any version of Visual Studio before? If SQL Prompt used to find the database connection in Visual Studio for you, and doesn't now with SSDT queries, then that's useful information for us and we'll try to improve it in a future release.
Regards,
Paul / comments
Thanks for the feedback Jeff. It's good to see that you've got SQL Prompt working in your environment now.
SQL Prompt in Visual Studio sometimes has problems automatically identifying the database...
That's very strange. Maybe one of the SQL Prompt local configuration files has got something wrong in it, so renaming the %LocalAppData%\Red Gate\SQL Prompt 5 out of the way could be worth a try. You won't need to reinstall SQL Prompt.
In that directory, RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml has an entry <CandidateListColumnDivider>, which controls how far across the grey text should start. Although the user interface shouldn't let you move the grey text completely out of the way, if something has caused this value to be outside the range of 0.125 to 0.875 then the grey text could disappear. For instance, I manually edited the value to 1.0 and couldn't see the grey text at all.
Renaming the directory as above will reset SQL Prompt's settings, but you could also take a look inside that XML file to see if there is an odd value there. / comments
That's very strange. Maybe one of the SQL Prompt local configuration files has got something wrong in it, so renaming the %LocalAppData%\Red Gate\SQL Prompt 5 out of the way could be worth a try. ...
I'm sorry, that's not something we have ever seen before [image] . In my copy this grey text is there fine. Could you post more details about your SSMS version?
If you uninstall and downgrade to the previous version 5.3.0.3, does the grey text come back again?
Thanks,
Paul / comments
I'm sorry, that's not something we have ever seen before . In my copy this grey text is there fine. Could you post more details about your SSMS version?
If you uninstall and downgrade to the pre...
Hi rre,
Do you mean where it says "SELECT * FROM fragment" in grey on the right of the suggestions box? I still see this text on my machine with SQL Prompt 5.3.2.2.
If the object definition box is missing (the extra box that flies out with the full expansion of the snippet) then ensure that "Display object definitions" in SQL Prompt 5 > Options... > Behavior is checked.
Regards,
Paul / comments
Hi rre,
Do you mean where it says "SELECT * FROM fragment" in grey on the right of the suggestions box? I still see this text on my machine with SQL Prompt 5.3.2.2.
If the object definition box is...
Hi PDinCA,
I agree that it's pretty annoying to be asked to save these ALTER scripts on shutting down SSMS, when you have no need to do so (especially if you've been hitting F12 many times during the session). This is an issue we've logged before as SP-3443.
Unfortunately it doesn't seem to be a trivial fix as you might think. Anything SQL Prompt does with query tabs and suchlike involves using SSMS's undocumented API, so it may be tricky to work out how to unset the "modified" flag, if indeed it can be done at all. / comments
Hi PDinCA,
I agree that it's pretty annoying to be asked to save these ALTER scripts on shutting down SSMS, when you have no need to do so (especially if you've been hitting F12 many times during t...
I'm glad that's working well for you.
Although SQL Prompt often stops suggesting with invalid SQL, it does suggest tables after SELECT FROM, possibly deliberately so that you can enter the table name before the columns as you're trying to do.
Nothing has changed in this area since previous versions except the partial matching. I think the problem is just the combination of using Space as a completion character and having tables (or views) that contain the string "From". / comments
I'm glad that's working well for you.
Although SQL Prompt often stops suggesting with invalid SQL, it does suggest tables after SELECT FROM, possibly deliberately so that you can enter the table na...