Comments
Sort by recent activity
Hi rldawg,
I see your point: the partial matching is now suggesting more items and therefore has a better chance of matching one of your tables or views when you really wanted the word FROM.
The keyword FROM itself is not being shown because it's not valid SQL straight after a SELECT -- if it were, then FROM would be the top choice.
One option would be to use the ssf<tab> snippet to start your queries. This puts in SELECT * FROM and offers you the table list straight away (saving keystrokes!). Then, when you want the columns, you can either go to the * and press Tab to expand them all, or delete the * and press Ctrl+Space to get the column list as normal. You can edit the ssf snippet to include a newline by going to SQL Prompt 5 > Snippet Manager.... Alternatively you could format the SQL afterwards with Ctrl+K Ctrl+Y.
Another option is to create your own snippet (e.g. sf) that contains this:
SELECT
FROM
(with a space after the FROM). Then when you type sf<tab> it'll show you the table list immediately, giving you your previous behaviour as well as saving keystrokes.
Finally, you could stop using Space as a completion character, if your fingers can be retrained :-). Then the word FROM would come out fine when you type it, without completing to anything. / comments
Hi rldawg,
I see your point: the partial matching is now suggesting more items and therefore has a better chance of matching one of your tables or views when you really wanted the word FROM.
The ke...
Hi njahncke,
Do you have SSMS Tools Pack installed as well? This has a SQL Snippets option, which by default has "I" as a snippet for INSERT and Enter as the snippet insertion key.
If this is the case then you can disable SSMS Tools Pack's snippets at SSMS Tools > SQL Snippets > Options....
Regards,
Paul / comments
Hi njahncke,
Do you have SSMS Tools Pack installed as well? This has a SQL Snippets option, which by default has "I" as a snippet for INSERT and Enter as the snippet insertion key.
If this is the ...
Hi PDinCA,
Yes, you're right. 5.2.8.2 is now the latest version, although I haven't yet added a forum post for it. That link above pointed to the latest download, not 5.2.6 specifically. I've changed it now to avoid confusion.
Regards,
Paul
P.S. I know from your other post that you've been having some weird login issues that seemed to appear first in 5.2.8. We're still investigating that one as it is puzzling. / comments
Hi PDinCA,
Yes, you're right. 5.2.8.2 is now the latest version, although I haven't yet added a forum post for it. That link above pointed to the latest download, not 5.2.6 specifically. I've ch...
Hi Jason,
Thanks for your report.
There were some problems with formatting selected text that were inadvertently introduced in SQL Prompt 5.2.2. On Friday 24th we released 5.2.6 that we believe fixes this issue, so please give it a go and let us know if it improves things for you.
You should be able to get 5.2.6 by going to SQL Prompt 5 > Help > Check for Updates.... Alternatively you could download the new version from the Red Gate website.
Regards,
Paul / comments
Hi Jason,
Thanks for your report.
There were some problems with formatting selected text that were inadvertently introduced in SQL Prompt 5.2.2. On Friday 24th we released 5.2.6 that we believe fi...
Hi duhitsd,
We think this is due to a permissions problem when trying to update SSMS to add SQL Search's Ctrl+Alt+D keyboard shortcut.
Could you check if you have write access to the following directory?
%AppData%\Microsoft\Microsoft SQL Server\100\Tools\Shell
The particular files concerned are Current.vsk and User.vsk.
Regards,
Paul Stephenson
SQL Search Project Manager, Red Gate / comments
Hi duhitsd,
We think this is due to a permissions problem when trying to update SSMS to add SQL Search's Ctrl+Alt+D keyboard shortcut.
Could you check if you have write access to the following dire...
Hi Klaus,
It's the same notification list, so you'll get the email when we send it out.
SQL Prompt has supported VS2010 (to some degree) since version 5.0. You're right that Denali is based on VS2010, but we have to write special code for each version of SSMS and each version of Visual Studio that we want to support. There are other differences too: for example, Visual Studio doesn't have an Object Explorer, which is used for quite a few Prompt features. Unfortunately it's not trivial to support new environments!
Regards,
Paul / comments
Hi Klaus,
It's the same notification list, so you'll get the email when we send it out.
SQL Prompt has supported VS2010 (to some degree) since version 5.0. You're right that Denali is based on VS2...
The SQL Prompt team is working on getting support for SSMS "Denali" at the moment. We hope to get a pre-release version for people to try out in the next few weeks.
If you're not on the list already, please sign up for early access notifications if you want to try out SQL Prompt in SSMS Denali before we release it.
Note that SQL Search will not work in Denali yet -- this is likely to happen at a later date.
Regards,
Paul / comments
The SQL Prompt team is working on getting support for SSMS "Denali" at the moment. We hope to get a pre-release version for people to try out in the next few weeks.
If you're not on the list alrea...
We've noticed that the installation of SSDT replaces the old SQL query windows with a new kind that SQL Prompt didn't understand. We'll be fixing this in a forthcoming release of SQL Prompt.
Qualify Object Names will require a connection to a server (via SQL Prompt 5 > Connect to Server...). Format SQL and Uppercase Keywords will work without a connection. / comments
We've noticed that the installation of SSDT replaces the old SQL query windows with a new kind that SQL Prompt didn't understand. We'll be fixing this in a forthcoming release of SQL Prompt.
Quali...
Hi splitpete,
This crash started happening when Microsoft updated SQL Azure. It occurs because the system tables and views that SQL Prompt looks for to gather information about DB objects do not all exist in SQL Azure.
We're working on SQL Prompt 5.2 now, and this release will prevent the crash dialog from appearing.
Please note that SQL Prompt doesn't officially support SQL Azure, although as the code-completion feature mostly seems to work we have left it enabled in the hope that it will be more useful than not.
Regards,
Paul / comments
Hi splitpete,
This crash started happening when Microsoft updated SQL Azure. It occurs because the system tables and views that SQL Prompt looks for to gather information about DB objects do not a...
Hi oleotis,
Did you buy SQL Prompt Standard Edition? The formatting features are part of SQL Prompt Professional Edition, so if you activate with a Standard license then they will be disabled.
If this is the case and you'd like to upgrade, please contact sales@red-gate.com. / comments
Hi oleotis,
Did you buy SQL Prompt Standard Edition? The formatting features are part of SQL Prompt Professional Edition, so if you activate with a Standard license then they will be disabled.
If ...