662 results found
-
2 votes
-
On-the-fly query keyboard shortcut
Similar to the query shortcuts built into SSMS with the number row...except you can set it on-the-fly, quickly and easily.
I'll let you guys figure out the details if you think it's a good idea. Basically I want the ability to give SQL prompt a query, and say, "please run this every time before running the highlighted query". But the configuration process needs to be FAST and EASY to help with rapid troubleshooting.
This is useful for variable declarations that are at the top of a script, but you need to run another part of a script separately.
1 vote -
Conditional Snippets - Either...logic in the snippet, or logic to decide which snippet to run
I have some snippets that I would like to be server specific. For example, we have two servers, each one has a sort of "support" database, but they do not have the same database name. But both databases have maintenance procs I like to use that do have the same name.
I'd like to have some way of saying "If I am on Server1, then run SnippetA, if I am on Server2 then run SnippetB"
OR
Allow something like this as part of the snippet:
$IF($SERVER$='Server1','String1','String2')$
3 votes -
wrap line at the limit, not at comma
When setting a line wrap at a number of cheracters, I would like to get the line at that long, and then wrapped. Not at the first comma. For example currently I get:
select firstname
, lastname
, email
, phonenumber
, country
, countryalias
, region
, gender... but I want to get:
select firstname, lastname, email, phonenumber, country
, countryalias, region, gender1 vote -
Support a personal library of full queries with named parameters
This idea is kind of between snippets and tab history.
USE CASE
I frequently need to diagnose issues with our data. This typically involves using on of a few dozen queries. Currently each time I need one of these I have to 1) check to see if I have a recent version in tab history; 2) load it from some .sql file I happened to have saved it; or 3) rewrite it from scratch. For 1 and 2 I then have to search for all of the places where I need to replace WHERE expression values with data specific to…1 vote -
Object preview tab size too big - SSMS uses 4 space tab, preview using 8 space tab
When hovering over an object name to view its contents...the tab size used in the code is much larger than what is being used in SSMS. So the formatting of the preview is completely messed up.
Maybe a setting to configure the tab size? Or maybe it can look up what SSMS is using?
1 vote -
Automatically add DROP TABLE IF EXISTS for #temp tables
It would be nice if SQL Prompt had a way to add in the code DROP TABLE IF EXISTS #table for temp tables. Ideally it would add the statement immediately before the table is created from a CREATE TABLE or SELECT INTO statement.
11 votes -
Add option to wrap lines when concatenating strings
Sometimes I set a variable equal to many strings concatenated together using the "+" syntax. When I format with Regdate, there is no option to wrap lines in this case. Everything ends up on the same line as the SET, so the lines often get very wide and go off screen.
It would be great if there was an option to wrap text if things got too wide horizontally.
One solution would be a setting to format concatenated strings like this:
SET @Variable = N'String1'
+ N'String2'
+ N'String3'4 votesHi Amanda,
Would the ‘wrap lines longer than X characters’ option in the formatting styles help with this?
Tim
-
Feature to make variable declarations persistent while testing
Allows you to define (on a per tab/session basis) a list of variables you would like to be declared before running the highlighted piece of SQL.
Reason: I like to put all of my "magic numbers" in variables at the top of the proc. This works great for code readability, but it's a pain to troubleshoot because now everywhere the variable is used, you need to copy that variable declaration above whatever code you are testing in order for it to work.
4 votesThanks for the suggestion Chad. We think this is a nice idea, we’ll wait to see how others in the community comment and vote before taking it forward.
Tim
-
auto complete set proc parameter defaults
when stored procedures have variables with defaults, your auto complete intellisense does not set the default. for example, if the parameter @a is an int = 5 in the creation of the proc, your auto complete says @a = 0 --int
3 votes -
When excluding schema / database from suggestions, if provide excluded schema, suggestions should still appear, but limited to that schema
So i specifically excluded our "temp" schema from my suggestions and it works brilliantly, however, when specifically want that schema, after completing the schema name it should show me the suggestion within that schema? -
Currently my options are to remove the "don't show suggestions" for the temp schema and then add it again after this session.2 votes -
Copy & Paste into temp table
I often need to work with data sets from Excel. Instead of doing a whole "Import Data" process I would like to copy from Excel & paste into SQL Management as a temp or persisted table.
1 vote -
Menu option: 'Normalize Line Endings'
Sometimes line-endings get messed up by source-control (looking at you Git) and "intellisense" will give you lots of green squigglies that you'd rather not commit to the branch.
A good menu option for SQL Prompt would be 'Normalize Line Endings' with a sub-menu selection of 'Windows' or 'Unix'. Then fire off a regex expression powered search and replace on the file. It's fairly easy to do manually with a Ctrl+Shift+F in Visual Studio, but in SSMS, it's more complicated to do so manually, I think.
Git does this to me once in a while, and I have to open the…
9 votes -
Closing parenthesis and content indention on APPLY/EXISTS not indenting
It seems that the contents and closing parenthesis of EXISTS and APPLY clauses is not being indented as I would expect. So either i'm weird....or Format SQL is doing it wrong?
I'm using (
.....this parentheses style
)What it's doing:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
.....SELECT *
.....FROM tblB b
.....WHERE b.Col1 = a.Col1
..........AND b.Col2 = a.Col2
..........AND b.Col3 = a.Col3
)What I expect:
SELECT *
FROM tblA a
WHERE 1 = 1
.....AND EXISTS (
..........SELECT *
..........FROM tblB b
..........WHERE b.Col1 = a.Col1
...............AND b.Col2 = a.Col2
...............AND…3 votes -
Snippet tags to insert other snippets
I like to get clever with snippets, and it would be great to be able to create dynamic snippets for different circumstances by being able to nest one snippet within the creation script of another. That way I can parse individual functionality in different snippets, but build them together to create more complex dynamic snippets without having to maintain the same basic code in multiple individual scripts.
I could see this working simply like:
snippet1:
DoThing;snippet2:
$snippet1$
DoMoreThing;2 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.
-
Refreshing suggestions (Ctrl+Shift+D) should apply to all databases, not just the current one
Currently, when refreshing suggestions with Ctrl+Shift+D, only the new changes in the current database are seen. To load the changes in another database (that I'm referring with a 3-part name in a query), I need to change the current database to that one, press Ctrl+Shift+D and then change the current database back to the original one. If it's the first time I'm accessing the other database (since starting SSMS), the changes are loaded when typing the 3-part name. However, if I had previously accessed the other database, refreshing does not work as I expect: it should drop the entire cache…
2 votes -
Indent AND/OR in WHERE/GROUP BY/etc. differently than ON clause
Support request #137199: Provide an option to indent AND/OR entries in a WHERE clause to line up indented, but leave AND/OR entries directly underneath ON clauses:
SELECT
t1.col5
, t2.col6
FROM
table1 t1
INNER JOIN table2 t2
ON t1.col1 = t2.col1
AND t1.col2 = t2.col2 -- AND is directly below ON clause
WHERE
t1.col3 = 'Test'
AND t2.col4 = 5 -- AND is indented underneath WHERE2 votes -
script insert as
Today’s mail from https://sqlquantumleap.com/2019/05/09/maximum-number-of-rows-for-the-table-value-constructor/
Shows as way around the 1000 rows limitation on the VALUES ()… statement.Please enhance SQL Prompts “Script as Insert” feature to use this method.
Currently SQL Prompt is scripting it like this, when the results window has more than 1000 rows:
CREATE TABLE #temptable( [id_user] int, [RowCnt] int, [mt] datetime)
INSERT INTO #temptable
VALUES
( 372, 2,N'2012-09-01T00:00:00')
INSERT INTO #temptable
VALUES
( 196, 2,N'2012-09-01T00:00:00')
INSERT INTO #temptable
VALUES
( 210, 2,N'2012-09-01T00:00:00')
…It can be done like this:
CREATE TABLE #temptable( [iduser] int, [RowCnt] int, [mt] datetime)
INSERT INTO #temptable
select *
from(
values…5 votes -
"drop user"
Highlight of today was when I ran
DROP USER MyUserIn the wrong (production) database.
Please add a warning to SQL Prompt, like your
"You're about to execute a DELETE statement without a WHERE clause"When you run a DROP USER or a DROP LOGIN statement on a production server. Not only does the user or login disappear, but also all rights granted to the user.
Maybe add the question “are you in the correct database?”
3 votes
- Don't see your idea?