Comments
Sort by recent activity
@SzymonOs We have just released a new version (v0.2.2) of the extension. Could you install that and see if it works? If not, there should be a log file in the following directory: C:\Users\[username]\.azuredatastudio\extensions\redgate.sql-prompt-0.2.2\logs\ Could you send that log file (or all of them is there are more than one) to sqlprompt.in.ads@red-gate.com and we'll investigate it further? / comments
@SzymonOs We have just released a new version (v0.2.2) of the extension. Could you install that and see if it works?If not, there should be a log file in the following directory:C:\Users\[username]...
@hlattanzio What you have done sounds correct. The AdsSnippets file should be the path to the file that ADS stores its user-specific SQL snippets in (usually C:\Users\hlattanzio\AppData\Roaming\azuredatastudio\User\snippets\sql.json). You can check this path by running Command palette -> Configure user snippets -> sql.json and then look at the path of the file that opens. The SSMSSnippetsFolder is the path to the folder that contains your snippets for SQL Prompt in SSMS (usually %localappdata%\Red Gate\SQL Prompt 10\Snippets). For both of these, you should be able to leave them as Default and the extension should still find them. If that isn't working, check what both paths are and set them explicitly in the ADS settings. If that still isn't working, can you drop us an email to sqlprompt.in.ads@red-gate.com? / comments
@hlattanzio What you have done sounds correct.The AdsSnippets file should be the path to the file that ADS stores its user-specific SQL snippets in (usually C:\Users\hlattanzio\AppData\Roaming\azur...
Yes, give that a try (make sure to put the path to the sql.json file in, not the directory). If that doesn't work, can you drop us an email to sqlprompt.in.ads@red-gate.com? / comments
Yes, give that a try (make sure to put the path to the sql.json file in, not the directory).If that doesn't work, can you drop us an email to sqlprompt.in.ads@red-gate.com?
Hi Simon, That's probably the SQL Prompt setting. There is a snippets file already within ADS for sql snippets. Could you check the path to that file using the the command palette: Command palette -> Configure user snippets -> sql [image] Adrian / comments
Hi Simon,That's probably the SQL Prompt setting. There is a snippets file already within ADS for sql snippets. Could you check the path to that file using the the command palette: Command palette -...
Hi Simon, Can you confirm the path to your Ads snippets file (Command palette -> Configure user snippets -> sql and then look at the path of the file that opens)?
Adrian
/ comments
Hi Simon,Can you confirm the path to your Ads snippets file (Command palette -> Configure user snippets -> sql and then look at the path of the file that opens)?
Adrian
Hi Mike, I've dug into this a bit more. It looks like a bug related to what context is chosen when the search is run. I suspect it is related to a bug in ADS that has yet to be fixed (we've reported it to Microsoft). Changing the database via the dropdown menu in the query window doesn't always change the context for the search (it appears to keep the context of the original database). Opening a new query from the right-click menu on the database in the tree does seem to make it work correctly, so I'd suggest you do that as a workaround for now. Adrian / comments
Hi Mike,I've dug into this a bit more. It looks like a bug related to what context is chosen when the search is run. I suspect it is related to a bug in ADS that has yet to be fixed (we've reported...
Hi Mike, Could you check what version of the extension you have installed? Also, if you change the database of the current query and do another search, does the scope change at all? Adrian / comments
Hi Mike,Could you check what version of the extension you have installed? Also, if you change the database of the current query and do another search, does the scope change at all?Adrian
Yes, it should be. / comments
Yes, it should be.
Yes, that is a typo. Well spotted, and thanks for letting us know. I've just fixed it. / comments
Yes, that is a typo. Well spotted, and thanks for letting us know. I've just fixed it.
Thanks for getting in touch. We are aware of an issue with SQL Prompt v10.1.1 and are currently looking into it. We will post an update when we have a fix. / comments
Thanks for getting in touch. We are aware of an issue with SQL Prompt v10.1.1 and are currently looking into it. We will post an update when we have a fix.