661 results found
-
Switch between Alias formats AS/=
A formatting feature to change syntax between these two forms
SELECT field1 AS Alias1, field2 AS Alias2 FROM table1
SELECT Alias1 = field1, Alias2 = field2 FROM table1
Ideally useable without having to invoke the "Format SQL" command.
Hopefully selectable as an enabled option within a Format SQL style set.I spend a non-trivial amount of time reformatting SQL code for leading/trailing comma placement and alias AS/= placement, this would be a HUGE help
7 votes -
Enhance shortcut that qualifies object names to also do cleanup
Qualify object names [Ctrl+B;Ctrl+Q] should also clean up three and four part column references
2 votes -
Secure tab history
Either detect and scrub passwords from tab history, or store the history files securely so they can't be copied by backup software and viewed as plain text on the drive without a password.
5 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 -
Additional options for formatting the ON constraints of a JOIN
It would be appreciated if you could enhance the SqlPrompt Formatting Styles functionality for the Clauses >>> JOIN section. I'd like the ON keyword to stay on the same line as the table-name, but when constraints are line-wrapped, I'd just like them to be "normally" indented.
Presently, the only way to get close to this behavior is to check the "Place ON keyword on new line" checkbox and set "ON keyword alignment" to "Indented". But I don't want that box checked.
3 votes -
Show SPID in tab history for open tabs
For tabs with an open connection, show the SPID # in the list on the left side
2 votes -
Allow searching with regex in "SQL Search"
Currently it is hardly possible to search for column assignments like "Column1 = 0". The results include any words having zero.
This request is similar to the "allow multiple keywords searches", but it is for a button named "SQL Search" instead of "Tab History".
Either treat "match whole words only" as the entire search text entered is matched exactly or introduce another checkbox "Search as Regex" to handle this scenario.
1 vote -
Allow a Dark Theme for the Toolbelt GUIs
Allow dark theme for all GUI interfaces in Prompt.
2 votes -
Copy as where
It would be very useful to be able produce where clause from copied horizontal selection from the results grid. For example from the uploaded image, where clause should be
WHERE CTA.TRANSACTIONDATE = '2021-06-27'
AND CTA.TRANSACTIONTYPECODE = 52
AND CTA.ITEMCODE = 1500012200
AND CTA.ITEMBARCODE = '8001841964966'
AND CTA.YOURCOMPANYCR = 104183
AND CTA.OTHERENTITY_CR = 460842 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 -
ADS wildcard extension
Please add the wildcard extension (select * => select col1, col2, ...) to SqlPrompt in ADS, the same as it works in SSMS.
6 votes -
Debugger for SQL Code
After removing of SQL Code debugging features beginning with Management Studio 18, it would be quite welcome to have this feature in SQLPrompt.
Other competitors are already providing debugging.9 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 -
In the tables population dialog allow more filtering options - say, filter by schema, by name, etc
Allow more filtering options for populate tables with data tool.
1 vote -
For the SQL Compare tool allow to copy warnings texts
My idea is for the SQL Compare tool: when the warnings are displayed, it would be helpful to be able to copy text of these warnings to deal with them
1 vote -
"Manage Code Analysis Rules..." should also be available from the "Options..."-menu
All setup-options, except "Manage Code Analysis Rules..." seems to also be available from the "Options..." menu, which is nice ...
1 vote -
Prohibit SQL execution in case of UPDATE/DELETE without clause
At the moment a user is warned before executing a potentially dangerous operation.
However, junior devs might accidentally just press enter without thinking twice.
Please add functionality to PROHIBIT execution besides WARNING (like SSMS Boost has) so that junior devs can't make mistakes at all.
It would be fantastic if this would be possible.2 votes -
Suggest common day and time constants when a date/datetime field appears as a criteria
When a date or datetime field appears in a WHERE clause, include Suggestions of the following nature and dynamically substitute them upon selection with the nondeterministic or deterministic equivalents:
(I couldn't get my table to format nicely here - please see the copy in the uploaded file.)
(If it's currently 11am on Friday August 20 2021...)
Suggestion Nondeterministic replacement Deterministic replacement
now GETDATE() CAST('11am 20 August 2021' AS DATETIME)
today CAST(GETDATE() AS DATE) CAST('20 August 2021' AS DATE)
yesterday DATEADD(DAY, -1, CAST(GETDATE() AS DATE)) CAST('19 August 2021' AS DATE)
tomorrow DATEADD(DAY, 1, CAST(GETDATE() AS DATE)) CAST('21 August 2021' AS DATE)…1 vote -
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
- Don't see your idea?