Comments
Sort by recent activity
Hi mikecare
Did you install SSMS 17 RC2 first? When you install SQL Prompt it's only added into SSMS versions that are already installed. If you installed SQL Prompt before SSMS you'll need to reinstall SQL Prompt.
Cheers
Harry / comments
Hi mikecare
Did you install SSMS 17 RC2 first? When you install SQL Prompt it's only added into SSMS versions that are already installed. If you installed SQL Prompt before SSMS you'll need to rein...
Hi Torsten
SQL Prompt 7.5 beta now suggests MIXED_PAGE_ALLOCATION. You can download it from here.
Thanks again for your feedback. Please let us know if you have any other issues.
Cheers
Harry / comments
Hi Torsten
SQL Prompt 7.5 beta now suggests MIXED_PAGE_ALLOCATION. You can download it from here.
Thanks again for your feedback. Please let us know if you have any other issues.
Cheers
Harry
Hi jgonnering
Please could you email the screenshot to SqlPromptTeam@red-gate.com?
Did this issue only start happening when you upgraded to 7.4.0.471?
Cheers
Harry / comments
Hi jgonnering
Please could you email the screenshot to SqlPromptTeam@red-gate.com?
Did this issue only start happening when you upgraded to 7.4.0.471?
Cheers
Harry
Hi Torsten
Thanks for reporting these issues. It looks like our list and parentheses options aren't working properly.
We'll try and get this sorted for you!
Cheers
Harry / comments
Hi Torsten
Thanks for reporting these issues. It looks like our list and parentheses options aren't working properly.
We'll try and get this sorted for you!
Cheers
Harry
Hi hafnera
This had me spooked for a while!
SQL Prompt has changed "SELECT id" to "SELECT Id" when declaring @InsertRecordJSON. This is changed to match the casing of the column defined in #Test because "SQL Prompt > Options > Format > Actions > Apply casing options" is on. This causes the last SELECT to fail because you've got 'strict $.id' rather than 'strict $.Id'. SQL Prompt doesn't change the casing in strings so it results in a mismatch. I think changing to 'strict $.Id' and then formatting should solve the problem.
I think SQL Prompt is working as intended here but please let me know if I've misunderstood what's happening!
Many thanks
Harry / comments
Hi hafnera
This had me spooked for a while!
SQL Prompt has changed "SELECT id" to "SELECT Id" when declaring @InsertRecordJSON. This is changed to match the casing of the column defined in #Test be...
Hi Torsten
I can't tell where the additional spaces are in your example. Please could you highlight where they are? Sorry if I'm missing something obvious!
Many thanks
Harry / comments
Hi Torsten
I can't tell where the additional spaces are in your example. Please could you highlight where they are? Sorry if I'm missing something obvious!
Many thanks
Harry
Hi paulo29
The SQL Prompt installer can only add SQL Prompt into the versions of SSMS that are present at the time. To install into SSMS 2016 you'll need to run the SQL Prompt installer after you install SSMS 2016. As you're on the latest version this may require you to uninstall SQL Prompt first.
Sorry for the inconvenience. Unfortunately we don't have a better way to do it at this time.
Harry / comments
Hi paulo29
The SQL Prompt installer can only add SQL Prompt into the versions of SSMS that are present at the time. To install into SSMS 2016 you'll need to run the SQL Prompt installer after you i...
Hi ratra, sqldelo
Sorry for the delayed response. We've just released SQL Prompt 7.4 beta here which adds support for SSMS 17.
Cheers
Harry / comments
Hi ratra, sqldelo
Sorry for the delayed response. We've just released SQL Prompt 7.4 beta here which adds support for SSMS 17.
Cheers
Harry
Hi J L
Sorry you're having problems with SQL Prompt.
Can I check if you're using the new formatting styles? The new formatting feature which should support CREATE OR ALTER is not on by default. You can turn it on in the options menu (SQL Prompt > Options > Labs > Experimental features > Use new formatting styles)
Cheers
Harry / comments
Hi J L
Sorry you're having problems with SQL Prompt.
Can I check if you're using the new formatting styles? The new formatting feature which should support CREATE OR ALTER is not on by default. You...
Hi a.higgins
Sorry you're having problems with the expand wildcard feature.
a.higgins wrote:
Is there a way for SQL Prompt to correctly identify the columns / data types / whatever from the OPENQUERY syntax?
SQL Prompt doesn't populate its column list with results from OPENQUERY which is why those columns don't get inserted when expanding the wildcard. However SQL Prompt can retrieve columns from tables on linked servers when specified with the 4 part name: SELECT SomeColumn
INTO #TempTable
FROM LinkedServer.Database.Schema.Table
For this to work "SQL Prompt > Options > Suggestions > Connections > Load suggestions for linked servers" must be on.
a.higgins wrote:
Failing that, can SQL Prompt abort the wildcard expansion when it fails to identify columns from one or more tables (similar to the way it did in the isolated #TempTable select above)?
Currently SQL Prompt doesn't expand wildcards when it thinks there are no columns. Your suggestion to not expand the wildcard if Prompt fails to find columns in any of the tables in a JOIN seems sensible to me.
I hope we can solve this for you soon. Until then it's possible to stop Format SQL expanding wildcards by unchecking SQL Prompt > Options > Format > Actions > Expand wildcards. Expanding wildcards can be done separately from the SQL Prompt menu (keyboard shortcut: Ctrl+B, Ctrl+W) and will be limited to highlighted code if there is any.
Many thanks
Harry / comments
Hi a.higgins
Sorry you're having problems with the expand wildcard feature.
a.higgins wrote:
Is there a way for SQL Prompt to correctly identify the columns / data types / whatever from the OPENQU...