153 results found
-
Format on Save
Allow an option when saving / running a file that you format the sql to the format selected. Will make sure the whole team follow the standards and does not forget to run the formatter.
2 votes -
Align SET statements around = sign
I am a brand new user (1 day) for SQL PROMPT. I managed to get my parameter statements to align, but there is no option on my custom formatting style to align my set statements. See the attached jpg. Trying to get it to look like the yellow highlighted area.
2 votes -
Have formatting features for cross join match those of left/right/inner join
I have set up rules to format as such:
Select *
From Employees e Join
People p On e.PersonID = p.PersonID;Each table/view object aligned on a new line. However, when I convert to a "cross join", they don't generate a new line, they concatenate on the same line, like such:
Select *
From Employees e Cross Join People p;2 votes -
Additional options for formatting a GROUP BY clause
It would be appreciated if you could enhance the SqlPrompt Formatting Styles functionality. I believe this would go in the STATEMENTS >>> Data (DML) section.
I'd like to continue using the "If there are multiple expressions" item of the "Place GROUP BY / ORDER BY expression on new line" drop-down. But I'd like those expressions to be indented; they presently all left-align to the GROUP BY.
Also, while you're there, it seems that it would be good to also have add an "If longer than wrap column" option to the above-mentioned drop-down.
2 votes -
Refactoring an INSERT statement into an UPDATE statement with SELECT
Be able to refactor INSERT statement into UPDATE statement that has SELECT rather than VALUES i.e. "insert into xxx select from".
2 votes -
DDL Parentheses Formatting should apply to VALUES clause of INSERT Statements - Bug?
The current parenthesis options I have set for an INSERT INTO (DML) statement, only appear to work for the list of columns, but NOT for the list of values in the VALUE clause. I'm unsure why this behaviour is different, but this inconsistency seems like a bug.
I have provided a screenshot where you can clearly see the parentheses are not aligned correct in comparison with the INSERT statement.
Ultimately I would like for the formatting to be overall consistent.
2 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 ...2 votes -
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)
2 votes -
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 -
Have Formal SQL Actions be included in the formatting style file.
Have Formal SQL Actions be included in the formatting style file. This way when a team shared a standard we do not have to share the file and screen shots of the Options menu to manually sync to maintain team consistency on code checkin.
2 votes -
Make the "Enclose identifiers within square brackets [ ]" option persist
Currently in Visual Studio the option to "Enclose identifiers within square brackets []" option will be set to true on startup requiring a user to turn it off every time they load Visual Studio.
This option when set to false should remain that way even after a restart of Visual Studio the same way it does in SSMS.
2 votes -
Option / Action to remove square brackets from types
I prefer types without square brackets ( INT vs [INT], for example).
If using square brackets for identifiers in the format options, there is no quick way to remove these.
My work-around is -
1. Apply Format Style option "Add/remove brackets + Remove Unnecessary brackets"
2. Format the block of code
3. Apply format Style option "Add/remove brackets + Add brackets to all identifiers"
4. Format the block of code
5. restore format Style option to original choiceIt would be nice to have a single action to do this, or to have a separate option in format styles to…
2 votes -
Option to Omit Formatting of Comments
Option (such as a check box) to omit active style formatting of comment lines between /* and */. Similar to SQL Prompt formatting off/on without the added code lines.
2 votes -
Add option to choose Single/Multi-line script for INSERT and EXECUTE statements
Currently SQL Prompt inserts SQL full INSERT script or EXEC SP in multiline while it might be useful for INSERT statement, but most of the times I have to realign them into a single line. It would be good if we have the option to choose wheather to add statement in single line or multi line? and its more usefull if we have shortcut to switch the inserted statement between formats?
2 votes -
Use SQL Prompt editing settings in other tools (like MultiScript)
When I am composing a script in Multi-Script, I'd like to have the editing settings available. Include variable/column name completion, keyword formatting, indention, etc..
2 votes -
Begin statement is not starting on a new line within an If statement. Please allow this in format styles. The option is there but it doesn't
When Place Begin - End statements on new line is selected it doesn't appear to work as part of an If statement. This makes the begin and end difficult to find
2 votes -
Convert IIF to CASE
We have code littered with IIFs that we would like to convert to CASE. Logically this is straightforward, but achieving it swiftly is proving more difficult. A regex takes care of the simple ones, but the ugly ones with nested functions across multiple lines and all sorts are proving far more difficult.
Would it be possible to add a feature to SQL Prompt to refactor IIFs into CASE statements? Thanks
2 votes -
CTE column list formatted like the columns in the AS list
The columns listed in the CTE are not formatted like the columns in the AS clause. On larger CTE's, the listed columns may be hundreds or characters long so we get
with xx
( a, b, c, d, e, ...) AS
(Select a,
b,
c,
d,
e,
...2 votes -
Option For Aliases (Only For Custon Alias)
Hi
it is better to SQL prompt use only aliases define with user.need option in Aliases : Only For Custom Aliases
Sorry For My Bad English
2 votes -
"Remove Square Brackets" option
The "Remove Square Brackets" option does not work for "CREATE EXTERNAL TABLE" statement.
Please try this option with the example below and nothing happens.
CREATE EXTERNAL TABLE [ft].[Account]
(
[AccountId] [bigint] NOT NULL,
[AccountType] [nvarchar] (50) COLLATE NOT NULL,
[AccountCreatedDate] [datetime2] NOT NULL
)
WITH
(
DATASOURCE = FinancialDB,
SCHEMANAME = 'Account',
OBJECT_NAME = 'Account'
);2 votes
- Don't see your idea?