663 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.
9 votes -
Execute current statment
Shift-F5 is great but I think this change could make it better.
Before I discovered Shift-F5 and when I had multiple sql statements in my window, I would select the block of sql I wanted and hit F5 to just execute that code block. Then I discovered Shift-F5 and I no longer had to select my sql block it was done for me - but what it doesn't do is actually select the code block, instead it just highlights it in green and executes it. So if you just do an F5 (out of habit) after a Shift-F5 it won't…9 votes -
Auto generated INSERT needs a column blacklist
Add the ability to exclude columns from appearing in the auto-generated INSERT statements. I have to manually remove certain columns every time.
9 votes -
Remember search settings in Tab History
At present, when I search (and I hate that the search opens as a new screen), I have to click "advanced search", and select object type of "queries" (I'm really not interested in the query history, I'd rather turn it off but there's no option to do that)
The one thing that would be most useful thought would be to remember the advanced settings between uses - or maybe allow them to be saved as a search default. This would go some way to address the poor user interface changes that have made the new SQL History much harder to…
8 votes -
Auto-Correct TOP to include Parenthesis
Add an Enable checkbox in the Style Sheet | Global | Parenthesis settings.
When SQL Prompt encounters the 'old style' usage of TOP, without parenthesis, automatically enclose the apparent 'what' in parenthesis.
8 votes -
SQL History
Over the years my Tab/Sql History became huge, and it is working very slow. I am looking for a way to clean up.
1. There is no way to select multiple lines to delete. Delete is available only for one row. For example, every ALTER PROCEDURE creates history. I don’t need it at all. I would like to find all of them and delete.
2. There is no functionality to compress and reindex Sql History database.
3. Ironically “Send Feedback” link on a bottom of screen leads to nowhere.8 votes -
Restore the working "Open in Excel" functionality for exporting numbers.
In version 10.12.1 and older the "Open in Excel" functionality actually created a Excel file where numbers were numbers and could be used in formulas like SUM. Starting in, I think, 10.12.4 you started exporting all numbers as a string. That completely breaks the usability, as you can then no longer make a formula using the numbers. (And while Excel offers the option to convert them back to numbers, it would be a pain to do it for each column that needed it and it takes FOREVER.)
At this point I will have to stay on 10.12.1 and not upgrade…
8 votes -
Allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting
SQL Prompt should allow block comments /* SQL Prompt formatting off */ to disable T-SQL formatting.
Single line comments are a pain when tuning queries. I would always use block comments in my code except when I don't want SQL Prompt to not mess with certain T-SQL it does not format to my standards.
Blocking formatting should support both type of comments.
/* SQL Prompt formatting off */
-- SQL Prompt formatting off8 votes -
Full support for Azure SQL Managed Instance in SQL Prompt
SQL Prompt should fully support Azure SQL Managed Instances. This includes offering suggestions for all objects (such as system functions, tables, views, etc) which are usable in Managed Instances. For example, CURRENTTIMEZONE and CURRENTTIMEZONE_ID (which were recently implemented in SQL Prompt, but only for Azure SQL Database). All other functions I've tried seem to be working fine, but it would be nice to know that Azure SQL Managed Instance is officially supported by SQL Prompt.
8 votes -
set default join conditions
I work on the same databases on a regular basis. Many do not have foreign keys and do not used identically named column names in tables that I'm joining.
I repeatedly have to specify the same several columns in the join condition.
I'd love a way for SQLPrompt to either remember join clauses I've previously used, or allow me to specify default join conditions for pairs of tables (or both).
8 votes -
Optional column alias when expanding wildcards
When SQL Prompt gives you the option to expand wildcards by typing a TAB, can you make it possible to add a modifier key (say Alt-TAB or Ctrl-TAB) that will generate aliased column names based on the table name?
For example, on an insert or update statement, we can use the OUTPUT clause to capture the changes made to a table. So, currently, typing Deleted.* and pressing TAB will generate columns such as
Deleted.Id,
Deleted.ModifiedDate,
Deleted.Description
and so on.It would be more useful to have
Deleted.Id as DeletedId,
Deleted.ModifiedDate as DeletedModifiedDate,
Deleted.Description as DeletedDescription8 votes -
Option to not square bracket aliases
It would be nice to have an option to not but square brackets around aliases as it's our style to not do so. We find it makes the aliases unnecessarily long,since most of our aliases are 1 or 2 letters.
For example
SELECT
T.[TableId],
T.[Name]
FROM
[dbo].[MyTable] Tvs
SELECT
[T].[TableId],
[T].[Name]
FROM
[dbo].[MyTable] [T]Currently we have to go back and rename an alias to itself so that the square brackets go away.
8 votes -
column alias by column name
Feature to automatically add column alias with the name of the column.
E.g.:SELECT Column1
FROM Table1 AS t1changes to:
SELECT Column1 AS Column1
FROM Table1 AS t1If the name can not be found add a dummy-alias like Exp1
8 votes -
Allow for Tab History search with date / server criteria
I use Tab History daily and have come to rely on it to find queries that I thought I was only going to need one time, but end up needing again. It would be great if you could use other things to search instead of just keyword. I would like to be able to select a date or date range (for example, I know I ran that query last month, or 3 months ago) and server (we have multiple servers with the same data sets so it would be nice to be able to filter to the server you know…
8 votes -
Purge tabs
At the moment to purge old tabs you need to open the tab history window and scroll to a certain point and right click and choose "Remove tabs older than this"
This can be a bit tricky so instead could we have a button (perhaps in options?) that will prompt you for a date and purge items last closed before that date.
8 votesThanks for the suggestion!
We’re actively reviewing this suggestion alongside some others for Tab History. We’ll update again here when we progress.
-
code folding
Enabled Intellisense conflicts with SQL Prompt and needs to be disabled. This also disables Code Folding feature (Outline Statements) of SSMS, which is very useful for large coding projects.
It would be helpful if SQL Prompt were to offer the similar feature.8 votes -
Trim white space
Please add an option be added to SQL Prompt to trim all white space.
Ideally, the following would be supported:
- Ability to execute against a query window or block of selected code
- Available as a stand-alone shortcut
- Can include as part of a Format SQL style
- Option to remove a) leading spaces, b) trailing spaces, c) both8 votes -
Allow custom rules for code analysis
SQL Prompt has the ability to catch and warn about Update statements without Where clauses.
How about something similar that catches and warns about security commands like Grant or Deny.
8 votes -
align aliases
Please, separate options to align aliases for columns and tables..... I love aligned column aliases, but table aliases advance too far right, unnecessarily.
8 votes -
Automatically create variables for use with generating full INSERT statements
Currently the behavior for inserting a full INSERT statement is that it produces something like this:
INSERT INTO dbo.ContactPictures
( InterActionPersonalContactID ,
InterActionFirmContactID ,
ImageFileStoreFilePathSegment ,
Source ,
ManuallyCreatedByUserAccountName ,
DateTimeLastUpdated
)
VALUES ( 0 , -- InterActionPersonalContactID - int
0 , -- InterActionFirmContactID - int
'' , -- ImageFileStoreFilePathSegment - varchar(256)
'' , -- Source - varchar(20)
N'' , -- ManuallyCreatedByUserAccountName - nvarchar(40)
GETDATE() -- DateTimeLastUpdated - datetime
)Hard-coded values are rarely what's needed, though; it would be very useful if it could generate variables and use them in the statement, like this:
DECLARE @InterActionPersonalContactID INT = 0…
8 votes
- Don't see your idea?