689 results found
- 
CTE on new line with commas before items is adding an extra lineWhen using the Lists > "Place commas before items" combined with the CTE >" Place CTE name on a new line" options, the subsequent CTEs are getting placed on new lines after the comma is already on a new line, resulting in: WITH 
 myCte
 AS ( SELECT 1 a )
 ,
 mySecondCte
 ( Col1, Col2 )
 AS ( SELECT
 'Test' AS ThisIsAColumn
 , 'Test2' AS ThisIsAnotherColumn
 FROM Person.BusinessEntityContact )
 SELECT *
 FROM myCteI believe this combination of settings should be resulting in: WITH 
 myCte
 AS ( SELECT 1 a )
 , mySecondCte
 ( Col1, Col2 )
 AS ( SELECT…3 votes
- 
Place empty lines between BEGIN/END and their contentsThe Whitespace > "Empty lines between statements" option doesn't appear to consider BEGIN/END as separate statements from the code between them, resulting in formatting like: WHILE @@ROWCOUNT > 20 
 BEGIN
 IF @BusinessEntityID > 0
 DELETE FROM HumanResources.Employee_Temporal
 WHERE BusinessEntityID = @BusinessEntityID;
 ELSE
 BREAK;IF @OldId < 2000 
 RETURN @OldId;
 END;Please modify the behavior or provide another option such that the following result can be achieved: WHILE @@ROWCOUNT > 20 
 BEGINIF @BusinessEntityID > 0 
 DELETE FROM HumanResources.Employee_Temporal
 WHERE BusinessEntityID = @BusinessEntityID;
 ELSE
 BREAK;IF @OldId < 2000 
 RETURN @OldId;END; 2 votes
- 
Formatting style for CASE statement: on a new lineAdd a feature for the formatting styles for CASE expression. Currently the formatting is so strange, it adds indents that don't make sense. 
 It should have the possibility to add CASE on a completely new line.Please add :Start expression on a new line or something… 3 votes
- 
subI would like to be able to check a box and always indent a sub-query. currently formatting a query works like this: 
 SELECT *
 FROM dbo.tbl1 AS a
 INNER JOIN(SELECT ID FROM dbo.tbl2 WHERE value = 'y') AS b ON a.id = b.idwhen the paren is set to inline the open paren and indent the content with the indent parentheses contents checked. I would rather have a checkbox to force the sub-query to format like this: SELECT * 
 FROM dbo.tbl1 AS a
 INNER JOIN (
 SELECT ID
 FROM dbo.tbl2
 WHERE value = 'y'
 ) AS b ON a.id =…1 vote
- 
Close pop up windows when holding down the control key while editing sql in SSMSWhile editing code in SSMS, i often find I want to use control key navigation (ctrl - left arrow for example) to navigate to a different part of the text i'm editing, but a pop-up intellisense window has arrived and instead of moving to the start of the word i'm editing, its trying to make me choose things from its pop up. It would be nice if ctrl key navigation would auto close the intellisense window so I could continue moving around the text of my query instead of having to hit escape all the time to close the pop… 3 votes
- 
Add system versioned table scriptingAdd system versioned table scripting 3 votes
- 
SQL Prompt - More Granular Suggestion. WHERE AND / CASE ANDSQL Prompt - More Granular Suggestion. WHERE AND / CASE AND Would you add a couple of settings that give users more granular control in formatting SQL Prompt, please? In the CASE section, please add a section on how to handle Case AND statements, if we want the AND on a new line or the same line, and where to Align the AND. Also, please add a checkbox to align any '=' signs, like CASE WHEN colA = 1 then 1 else. I'd like all = signs to line up when there are multiple WHEN statements. Also, Please add a… 3 votes
- 
One feature idea that I think would be great for many customers. Often I have a pasted column of data from Excel that i need to run a macroOne feature idea that I think would be great for many customers. Often I have a pasted column of data from Excel that i need to run a macro on in Notepad++ to add single quotes and commas. So that I can paste the string into a SQL “in ( ) " clause. It would be amazing if SQL Prompt had an option to convert that clipboard text right in SSMS. I think lots of people would find that a timesaver. 2 votes
- 
Allow indentation similar to nested JOIN when they are not written as nestedA nested join is indented additionally relative to the join that it is nested within: SELECT * 
 FROM Person.Address
 --INNER JOIN Person.StateProvince
 ----INNER JOIN Sales.SalesTerritory
 ------ON SalesTerritory.TerritoryID = StateProvince.TerritoryID
 ----ON StateProvince.StateProvinceID = Address.StateProvinceIDWhen joining the same tables but not writing them in a nested manner, there is no additional indentation: SELECT * 
 FROM Person.Address
 --INNER JOIN Person.StateProvince
 ----ON StateProvince.StateProvinceID = Address.StateProvinceID
 --INNER JOIN Sales.SalesTerritory
 ----ON SalesTerritory.TerritoryID = StateProvince.TerritoryIDIt would be nice to allow the same amount of indentation that would be used if the join were nested to be used when it is not nested: 
 SELECT *
 FROM…1 vote
- 
Separate VALUES style by first/subsequentIt would be nice to have an option to specify different styles when there is one set of VALUES compared to multiple. For example, I would like to use "Compact, indented) when there are multiple sets of VALUES: INSERT INTO Employees 
 ( id
 , FirstName
 , LastName
 , BirthDate )
 VALUES
 ( 2
 , 'Jane'
 , 'Doe'
 , GETDATE())
 , ( 3
 , 'Frederico'
 , 'James'
 , GETDATE());But compact when there is only one set of VALUES: INSERT INTO Employees 
 ( id
 , FirstName
 , LastName
 , BirthDate )
 VALUES
 ( 2
 , 'Jane'
 , 'Doe'
 , GETDATE())1 vote
- 
Option to Change != to <>Although used quite often, != is not ANSI compliant for NOT EQUAL. Have an option in SQL PROMPT Code Formatting to automatically replace != with the ANSI compliant <>. 2 votes
- 
Make Import / Export of options more flexible (xml file format or enable partial export of sections)I would like to be able to export (+import) only specific portions of the options. So that I - for instance - may only distribute my aliases or my coding style options to the team; not everything. The current binary format for the export file only allows for an all-or-nothing approach. So please 
 (A) Make the export file a xml-format, so we can filter it ourselves
 or
 (B) Add a dialog to allow us to mark the sections to be included into the export file via checkboxesThis would also likely solve other feature-requests: 
 - https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/46784125-export-snippets-to-text-file
 - https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/40966285-sql-prompt-setting-sharing
 - https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/39174019-import-and-export-aliases1 vote
- 
Format SQL & Entity Framework — making EF SQL easily readableI have the misfortune of trying to read an EF query. It would be extremely helpful if the «Format SQL» function in SQL Prompt could greatly reduce the verbosity and make the massively nested queries much, much easier to read. This is what I am doing by hand: • Replacing names like 'Extent6' with letters of the alphabet. I will go back later and replace these letters with more helpful names. Because the aliases of the table-valued objects are so long, so is there so much more text to plough through; • Removing aliases from columns whose names are identical.… 1 vote
- 
Aliases for synonymsWhen using a synonym, the alias name generated is based on the synonym orginal table, not in the synonym name. So, if I have a synonym named sch1.ShortTableName that maps on AnotherDatabase.sch2.TableWithLongAndComplexName If I write SELECT * FROM sch1.ShortTableName It ends being SELECT * FROM sch1.ShortTableName AS twlacn It would be good that in case of synonyms, the alias name was based on the synonym name, not on the source object name. Or to keep backwards compatibilty, to have a setting that lets us choos either to follow the synonym name or the source object name. 2 votes
- 
Allign all euals of a set part in an updatestatementAllign all equals of a set part in an update statement 2 votes
- 
Turn off SQL Prompt+ AIPlease can there be an option to turn off SQL Prompt+ AI. It is a pointless feature that I have found no benefit from. It locks up and crashes SSMS. It also it an extremely intrusive feature constantly displaying the icon next to the cursor 2 votes
- 
When setting tab colors, allow/disallow the status bar to mirror the tab colorI am color-blind and while tab coloring isn't as big an issue, the real estate of the status bar and font size makes certain color schemes that I use on tabs VERY difficult to read. I would love an option to select whether the tab color propagates to the status bar and possibly even separately set a different "default" color for the status bar. I know some have requested the status bar mirror the tab color but some of us color-challenged developers would rather not have that option. Note, the "default" color could be consistent across all environments rather than… 1 vote
- 
Fix SQL HistoryUser of SQL Prompt for some years now. Tab History was a "killer feature". I often have multiple instances of SSMS open, with a number of ad-hoc queries open not worth saving. When I log back in, for years, WITHOUT FAIL, ALL my queries, from ALL instances would re-open. Since "upgrading" to SQL; History, I am lucky to get one or two re-open. Complete pot luck. Even searching for known keywords to get them open again is hit and miss. I am losing a lot of productivity due to this downgrade. I have yet to experience any benefit from the… 16 votes
- 
Bring Back Tab HistoryTab History NEVER should have been replaced with SQL History, a very poorly received roll-out that angered many paying customers. The fact that Red-gate felt it necessary to re-brand the thing is indication enough that it wasn't simply an update to Tab history but a replacement. That said when you do something like this in a product people are paying for it should be rolled out as something new and not something that replaces an existing beloved feature. Perhaps after enough updates SQL history will be usable and thus tab history unnecessary but there's no telling how many updates that… 21 votes
- 
SQL Rule/Issue/Error SearchLike SQL Search, but SQL Error/Issue/Rule violation. 
 This would list all issues that exist in a database.
 Example: "Non-scalar subquery in place of a scalar value"Because these issues can cause major slowdown in queries, and it would be great to have a way to search a whole database to find these rather than having to open all the views, procedures, and functions to find all these things. 2 votes
- Don't see your idea?
