689 results found
-
INSERT INTO Wildcard
When doing an INSERT INTO it would be nice if you could type INSERT INTO TableName (*) then if you tabbed after the * it would expand out all the columns for that table.
10 votes -
Format dynamic SQL
We use a lot of dynamic SQL. I'd like to be able to format dynamic SQL that is in a string, eg. and NVARCHAR. e.g.
Input: DECLARE @sql NVARCHAR = '
SELECT foo from bar where foobar = ''foobarred''
'I'd like to be able to highlight the text inside the NVARCHAR for formatting. SQL Prompt would need to handle doubled quotation marks as in my example above.
19 votes -
Create new Setting to only enclose SQL Keywords in square brackets
I don't want to use brackets for my code (unless I have to). So, for example, dbo.Orders is fine, but dbo.Order isn't. It would be nice if SQL prompt caught this and automatically enclosed the SQL Keyword "Order" in square brackets (i.e. dbo.[Order] AS o)
54 votes -
Format CTE closing parenthesis
It would be nice to have an option under Formatting Style -> CTE to allow closing parenthesis behavior, just like the opening parenthesis one:
- Place closing parenthesis on new line
- Closing parenthesis alignment14 votes -
Align "then"
Please add an option to align "then" keyword and the expressions.
Current format:
declare@fooidint=(case
_______________________when@barId=7then2
_____________________when@barId=800then1
_____________________else5
_________________end
__________________);Suggested format:
declare@fooidint=(case
_______________________when@barId=7then2
____________________when@barId=800_then1
_____________________else________________5
________________end
__________________);15 votes -
Empty Line Before and After Multi-Line Statements
Complex multi-line statements are much easier to read when separated by an empty line above and below them. Please add an option to turn on "Empty Line Above/Below Multi-Line Statements".
5 votes -
grid aggregates
Results Grid aggregates
SUM, AVG, MIN, MAX and COUNT aggregates are shown
for selected range of cells in Results Grid open a new window with this reslults22 votes -
Detect the database compatibility version
When using SQL server 2016 with a database that has it's compatibility level set to 2012, I'm still being offered auto complete options for 2016 features. e.g. string_split
SQL Prompt needs to detect the database compatibility level and adjust it's intellisense accordingly.
3 votes -
Tab History - sort or filter on evironment
Allow me sort or filter the tab history list based on the environments that I have defined.
6 votes -
Match Visual Studio Themes
Visual Studio supports a Dark theme however Prompt doesn't match and still displays the standard white for suggestions.
22 votes -
Export all results to Excel, not just a single table
It would be awesome if the Results tab could be right-clicked (when results are in a grid), and then have an option to export all tables to Excel, with each table being in a new tab. Currently I can only export one table of results at a time to Excel, and if I need to do multiple tables then multiple sheets are opened.
25 votes -
Comment Word Wrap
Hi!
I would be nice to have the option to enable word wrap for the comments as well.
The number of maximum characters for the comment should be aligned with "Wrap lines longer than" for SQL statements.19 votes -
Outline for scripts
It would be very helpful if there was an outline for the script being edited. Say, a script has many "CREATE PROC"s. We could have a tree or a list or a drop-down, to view a list of CREATE PROCs and click to scroll to the section.
If a tree style is selected, this could be expanded into seconds inside each PROCs.
3 votes -
export to excel options
Hi - export to excel is a great feature. if it could be extended in 2 ways it would be even better.
copy the sql used to produce the results (and date, server info) into a separate tab called 'sql' or something. this way data extracts will be 'auditable' and re-runnable.
have some export options (top row = bold, highlighted, freeze top row). column autowidths applied.
the second one can be done with a macro in the excel template but would be a nice to have.
13 votes -
Discover metadata for OPENQUERY
When I use the OPENQUERY syntax to retrieve data across servers, SQL Prompt does not discover the metadata (column names, data types, etc.) of the fields returned.
My suggestion is that you add support within SQL Prompt to make metadata for fields retrieved by OPENQUERY available just like you do for linked servers.
7 votes -
Multiple rows of tabs
If I have more open tabs than can horizontally fit the window SSMS does not show all of them but instead there is a dropdown in the right upper corner. I would prefer if I could have multiple rows of tabs instead, like in VS. Since it does not seem likely that MS is going to implement that soon, can it be done in SQL prompt?
33 votes -
Keep pinned status
In SSMS 2016 you can now Pin tabs. When you close and re-open SSMS, it would be good if Tab History could remember, and restore, the pin status for each of the tabs as they are being restored.
42 votes -
Prefered server Connection List
When working all day long with serveral SQL servers, its really annoying to click on "change connection" button + enter the server name you want to connect to, and enter credential.... It would be really great we we would have a "server connection list" where we could build into settings.... So i could add all my server i'm use to connect everyday, and specifying the USERNAME + PASSWORD + Default DB..... So in one-two click, i could switch to another server really quicly
29 votes -
Bookmarks
Bookmarks is a feature of SSMS. But all my bookmarks are destroyed once the code is formatted. So, as SSMS' feature is not so good as I want I do suggest to implement this feature by RedGate.
3 votes -
Ability to generate SELECT test script from an UPDATE statement
When debugging an UPDATE statement, it would be handy if SQL Prompt could generate a test Select script that converts
UPDATE xxxxxx
SET SalesPeriod = dddddd,
SalesYear = yyyy,
CustomerCode = zzzzz
...into
SELECT dddddd as SalesPeriod,
yyyy as SalesYear,
zzzzz as CustomerCode
....Optionally, could include all columns involved in joins or WHERE clauses
11 votes
- Don't see your idea?