Activity overview
Latest activity by mbray
That did work. In fact I didn't even have to make a backup of the folder - I could see that one of the xml files in that folder (RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml) was empty. I exited SSMS, renamed it to bak, started SSMS again and everything seems back to normal. (RedGAte maybe should add some better error handling in this circumstance.) Thanks! / comments
That did work. In fact I didn't even have to make a backup of the folder - I could see that one of the xml files in that folder (RedGate_SQLPrompt_CommonUI_Options_UIOptions.xml) was empty. I exi...
REDGATE SUPPORT - My SQL Prompt no longer works - error during startup
Hi, earlier today I was using SSMS and it locked up while typing a SQL statement. (This has happened on occasion in the past.) However this time, after killing the SSMS process and restarting, I ...
BUG: InlineEXEC incorrectly treats $text$ as a substitution
If a procedure has code that includes $text$ (where 'text' is any word) then the Inline EXEC function incorrectly treats this value as a substitution, removing the $'s and highlighting the text.Exa...
Submitted Request #112188. / comments
Submitted Request #112188.
Hi Richard, thanks. I installed the new version, verified it is running in Visual Studio, but I'm still seeing the issue. Note that this issue does not occur in SSMS - only in Visual Studio. Here's a more specific set of procedures to reproduce:
In Visual Studio, open a new file using the template "Sql File"
Use the connect button to connect to a database (I simply pick one from my history)
Type "ALTER PROCEDURE" (or "AP" shortcut) and hit space - the list of procedures from the current database are listed
Clear the text, then type "USE <someOtherDatabase>" and execute. Note that the database dropdown should now list "<someOtherDatabase>" as the current database.
Clear the text, then type "ALTER PROCEDURE" (or "AP" shortcut) and hit space... the list of procedures in the intellisense dropdown are the same ones as listed previously, not the procedures from the new database
OPTIONALLY... manually switch the database back to the original using the database dropdown selector, then back to <someOtherDatabase". Now, repeating step 5, the intellisense dropdown list is correct.
Contrast this with manually switching the database, which works correctly:
In Visual Studio, open a new file using the template "Sql File"
Use the connect button to connect to a database (I simply pick one from my history)
Type "ALTER PROCEDURE" (or "AP" shortcut) and hit space - the list of procedures from the current database are listed
Clear the text, then click the database dropdown list to select <someOtherDatabase>
Type "ALTER PROCEDURE" (or "AP" shortcut) and hit space... the list of procedures in the intellisense dropdown is correctly listed as the procedures from the new database
/ comments
Hi Richard, thanks. I installed the new version, verified it is running in Visual Studio, but I'm still seeing the issue. Note that this issue does not occur in SSMS - only in Visual Studio.Here...
Intellisense not updating after USE statement
Using SQL Prompt 9.0.6.3580 from inside Visual Studio 2015... If I open a SQL file, and then choose a connection from my history, SQL Prompt provides proper Intellisense for my default database A...
FYI I had noticed the UI acting slowly, so I turned off code analysis, which definitely seemed to help. Then a few minutes later, I turned it on again, expecting it to slow down. At first, it locked up the UI for maybe a minute or so, but after that I didn't see any of the sluggishness. Maybe there are some data structures that are getting out of whack that get rebuilt when turning code analysis on. / comments
FYI I had noticed the UI acting slowly, so I turned off code analysis, which definitely seemed to help. Then a few minutes later, I turned it on again, expecting it to slow down. At first, it loc...
Minor CASE formatting issue
I'm using SQLPrompt 9.0.6.3580. Formatting CASE statements with negative WHEN values doesn't insert a space between WHEN and the value. For example, here's the result of formatted code:DECLARE @i...