663 results found
-
Make the column picker the default tab when suggesting columns inside a select
Make the column picker the default tab when suggesting columns when the ursor is inside a select statement.
2 votes -
Warn against reserved words in column names
Consider a table
CREATE TABLE [dbo].[ItemGroups](
[Group] [VARCHAR](25) NOT NULL,
[Description] [VARCHAR](25) NOT NULL)SELECT Group from dbo.ItemGroups ->
Incorrect syntax near the keyword 'Group'.
Would be nice to get a warning when a column name is a reserved word. Square brackets make the syntax valid but unnecessary if a column is named more accurately, e.g. ItemGroupCode
5 votes -
Unformat Query
Add a menu Item option to unformat a query. In other words take the query that is highlighted or every query in the script and convert them to be on a single line with only a single space between keywords, words, and operators.
This would be very useful for having to copy SQL into a table or other some object that shouldn't have normal formatting in it.
An option would be to double up all single quotes, so that the query can be placed between single quotes.6 votes -
drill down drill up from object display
In SQL Prompt, in the pop-up display for an object, allow drill down from an object reference in the popped-up display.
In the new feature showing dependencies, implement drill down (from the "uses" section) and drill up (from the "used by" section)
1 vote -
Properly format the start of a CTAS in Azure Synapse Analytics
SQL Prompt does not start a new line for the SELECT portion of a CTAS statement within Azure Synapse Analytics when there is a defined distribution or index using a WITH clause. Instead the SELECT statement is tabbed way over to the right.
6 votes -
Surround with, add to the list Select, Pivot, and I am sure there are more items like CTE
Surround with, add to the list Select, Pivot, and I am sure there are more items like CTE
1 vote -
refactor SELECT into CTE
The way I work when creating complicated scripts is creating all the SELECT statements and then convert them to CTEs of my final query.
It would be nice if you could convert SELECT into CTE7 votes -
Make auto savings of my open queries in case the program suddenly crashes
Sometimes my SSMS crashes. The Crash recovery of the program is not good enough. Would love to see "auto save" option that will save the open queries to history each time I'm idle for few moments. It would be much easier to recover than reproduce
4 votes -
Table Column Format Correction
In cases where there is SELECT DISTINCT or SELECT TOP(n) .. I would l like the option to format my table's columns to appear on the next line and indented 1 tab or set of spaces in from the SELECT and not necessarily aligned with DISTINCT or TOP in the line above.
SELECT DISTINCT
COLUMN1,
COLUMN2
FROM ...instead of
SELECT DISTINCT
Column1,
Column2
FROM ...3 votes -
Use formatter to create table of contents
It would be great to be able to use the formatter to create an automated table of contents based on some recognized commented pattern. For example, I could begin each section of code with:
--******
-- Title of section
--******Then after using the formatter it would see the commented section and add the line number for each section in the beginning of the script. I imagine something similar to MS Word's auto generated table of contents.
1 vote -
Ability to choose schema when there are multiple objects with the same name exists
Currently when SQL code is formatted, it will pick the first schema, if there are multiple objects with same name but having different schemas. It would be good if the choice is given to the user to choose which schema.objectname to use in this case.
Also it's better if we can exclude certain schema's to be considered during code format. (But want to see the intellisense. Only to exclude them during the code format)
3 votes -
Possibility to search for multiple keywords
It would be nice to search for multiple keywords in the Tab History. For example, I know I had a script to insert data from TableA to TableB, but I searching for TableA or TableB yields to much result (both are frequently use tables). Searching for "TableA, TableB" or "TableA*TableB" would be a good quality of life feature.
12 votes -
Swap commented / uncommented lines in selection
Using a shortcut to swap commented / uncommented lines in the sql script. This could be very helpful when we need to test (select / update) for the same source query.
Please check the screenshots
Thanks
6 votes -
Add your software to Microsoft Windows Package Manager (aka WinGet)
There is a new toy in town. Microsoft Windows Package Manager https://github.com/microsoft/winget-pkgs
I expect you to add your applications there. Thanks in advance4 votes -
Insert Snippet on New Query
Automatically insert a snippet as soon as you start a New Query in SSMS. I want all my developers to always start every script with a comment block with their username, date and a description of what the script is supposed to do. A shared snippet is already handy for this, but adding this could make it easier to build that habit for new team members.
2 votes -
Tie the SQL prompt Scripting to SSMS scripting
IN SSMS there is an entire list of scripting options (turn off/on collation, extended properties, etc). Can SQL Prompt read those options and format the scripts it generates based on those settings?
1 vote -
F12 to Create Table Script
F12 to Script views and stored procedures as ALTER is one of my favorite features. I would love it if F12 when I am on a table generates a CREATE TABLE script for that table.
2 votes -
Find invalid objects in script
Highlighting invalid objects is a nice feature, but it would also be nice to "find" invalid objects in a script.
Running SQL Format on a script with an invalid object in it runs fine and gives no error, it just doesn't prefix the object (like a table) with the schema.
It would be nice to have a quick and easy way to "go to next invalid object" or even for when you run SQL Format to have it bring up a warning saying "this/these object/s appear to be invalid".3 votes -
Script as Insert - Floats end up with innacurate data precision
After running a select on a table with a float(53) column, "Script as INSERT" from the right click menu on the results will script an insert with float(8) as the data type instead of float(53), presumably from the length of the column being recorded as 8 bytes when the float(n) is defined with n being bits.
Minor thing, but ended up causing issues with an equal statement since the floats had different precision when comparing to the original table.
1 vote -
Stop OPENJSON after CROSS APPLY from showing up on new line
I have included a Sample SQL script. This script shows the desired formatting. I can't find any way to prevent the OPENJSON from being sent to a new line. For example:
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY OPENJSON(OJ.Value)
WITH (ID int) AS CAOJbecomes
SELECT *
FROM OPENJSON(@JSON, '$.Doc') AS OJ
CROSS APPLY
OPENJSON(OJ.Value)
WITH ( ID INT ) AS CAOJ2 votes
- Don't see your idea?