695 results found

1. Warn about always true WHERE clauses such as ID = ID instead of ID = @ID

   It is common to create functions and stored procedures that have parameters with the same name as fields. Sometimes the @ is mistakenly skipped when creating a WHERE condition and you end up with something like ID = ID instead of ID = @ID. I would like intellisense that warns me about this type of error.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Intellisense  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Find Invalid Objects not working in v10.4.2 (SSMS 18.5, 18.6)

   Find Invalid Objects not working in v10.4.2 (SSMS 18.5, 18.6)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. materialise temp table (from SELECT INTO)

   I pick up LOTS of legacy code with SELECT INTO statements.

   sometimes they are into temp tables but also in physical tables.

   It would be great to be able to highlight the statement in the SQL and right-click and choose to automatically convert it into a TRUNCATE + INSERT INTO (whilst running the CREATE TABLE statement for me)

   for example:

   /This is the statement I start off with/
   SELECT TOP 10 *
   INTO dbo.example_table
   FROM sys.objects

   /SQL prompt pops up with dialog box to choose the table name and creates the table for me/
   CREATE TABLE [dbo].[exampletable]
   (
   [name] [sys].[sysname] NOT NULL,
   [object_id] [int] NOT NULL,
   [principal_id] [int] NULL,
   [schema_id] [int] NOT NULL,
   [parentobjectid] [int] NOT NULL,
   [type] [char] (2) COLLATE Latin1GeneralCIASKSWS NULL,
   [typedesc] [nvarchar] (60) COLLATE Latin1GeneralCIASKSWS NULL,
   [create_date] [datetime] NOT NULL,
   [modify_date] [datetime] NOT NULL,
   [ismsshipped] [bit] NOT NULL,
   [is_published] [bit] NOT NULL,
   [isschemapublished] [bit] NOT NULL
   ) ON [PRIMARY]
   GO

   /SQL Prompt then replaces the SELECT INTO with the following code/
   TRUNCATE TABLE dbo.example_table

   INSERT INTO dbo.exampletable (name, objectid, principalid, schemaid, parentobjectid, type, typedesc, createdate, modifydate, ismsshipped, ispublished, isschemapublished)
   SELECT TOP 10 *
   FROM sys.objects

   I pick up LOTS of legacy code with SELECT INTO statements.

   sometimes they are into temp tables but also in physical tables.

   It would be great to be able to highlight the statement in the SQL and right-click and choose to automatically convert it into a TRUNCATE + INSERT INTO (whilst running the CREATE TABLE statement for me)

   for example:

   /This is the statement I start off with/
   SELECT TOP 10 *
   INTO dbo.example_table
   FROM sys.objects

   /SQL prompt pops up with dialog box to choose the table name and creates the table for me/
   CREATE TABLE… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Use SQL Prompt editing settings in other tools (like MultiScript)

   When I am composing a script in Multi-Script, I'd like to have the editing settings available. Include variable/column name completion, keyword formatting, indention, etc..

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Tab History Window Behaviour

   Can the tab history window, when maximized, be made to consider the maximum screen size when it's popped out?
   I have monitors that have different resolutions and if I pop it out on my smaller screen it doesn't fit and I loose the top of the screen with the search and tabs - but most annoyingly that also means I loose the window bar so can't control the size either!

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Tab history  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. install

   Would LOVE SQL Prompt to do a silent upgrade, without the need to "promote" admin privledges, nor close Visual Studio / SSMS. Love the upgrades, but they are frequent, and the installation process is disruptive.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add option to choose Single/Multi-line script for INSERT and EXECUTE statements

   Currently SQL Prompt inserts SQL full INSERT script or EXEC SP in multiline while it might be useful for INSERT statement, but most of the times I have to realign them into a single line. It would be good if we have the option to choose wheather to add statement in single line or multi line? and its more usefull if we have shortcut to switch the inserted statement between formats?

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Smart Rename should be smarter about changing schema &table name

   When renaming both the table and schema name, and a table already exists w/ the old table name but new schema name, Smart Rename errors because it does not detect this conflict and tries to first rename the table to the conflicting table name.
   
   e.g., renaming stage.dboTable1 to dbo_stage.Table1 (and stage.Table1 already exists):

   EXEC sp_rename N'[stage].[dboTable1]', N'Table1', N'OBJECT'
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   ALTER SCHEMA [dbo_stage] TRANSFER [stage].[Table1]
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   

   would work if script instead did this:

   ALTER SCHEMA [dbo_stage] TRANSFER [stage].[dboTable1]
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   EXEC sp_rename N'[dbo_stage].[dboTable1]', N'Table1', N'OBJECT'
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   

   Note: your editor control apparently interprets special characters as HTML

   When renaming both the table and schema name, and a table already exists w/ the old table name but new schema name, Smart Rename errors because it does not detect this conflict and tries to first rename the table to the conflicting table name.
   
   e.g., renaming stage.dboTable1 to dbo_stage.Table1 (and stage.Table1 already exists):

   EXEC sp_rename N'[stage].[dboTable1]', N'Table1', N'OBJECT'
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   ALTER SCHEMA [dbo_stage] TRANSFER [stage].[Table1]
   GO
   IF @@ERROR <> 0 SET NOEXEC ON
   GO
   

   would work if script instead did this:

   ALTER SCHEMA [dbo_stage] TRANSFER [stage].[dboTable1]
   GO
   IF @@ERROR <> 0 SET NOEXEC

   … more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Smart rename  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Custom Formatting and Refactoring (API)

   I would like to expand upon suggestions others have made regarding adding custom formatting and analyzers.
   I have recently been trying to implement SQL Prompt for our team, and I have struggles with a lack of customization, opinionated options that don’t reflect our needs, and some bugs.
   What would have solved this issue for me would have been the ability to add custom formatters and custom analyzers.

   Custom Formatters
   Since SQL Prompt gets the position of tokens from IAlignmentProvider.FinalAlignmentForToken I suggest that the API couple simply be plumbed into this method, if a plugin is attached it would call the plugin with the current CalculatedAlignment and a context providing information about where in the script the token is located (in a select clause, from clause, sub query etc.), and the plugin would return a CalculatedAlignment and the process would resume as it currently does.

   Custom Analyzers
   Since SQL Prompt defines Interfaces for code analysis, I suggest that plugins should implement the IRuleProcessor and IRefactoring interfaces.

   It wouldn’t be the most elegant API, but it should be straight forward to implement.

   I would like to expand upon suggestions others have made regarding adding custom formatting and analyzers.
   I have recently been trying to implement SQL Prompt for our team, and I have struggles with a lack of customization, opinionated options that don’t reflect our needs, and some bugs.
   What would have solved this issue for me would have been the ability to add custom formatters and custom analyzers.

   Custom Formatters
   Since SQL Prompt gets the position of tokens from IAlignmentProvider.FinalAlignmentForToken I suggest that the API couple simply be plumbed into this method, if a plugin is attached it would call the… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. SQL Prompt Setting Sharing

    Provide an easier way to share SQLPrompt (snippet/code formatting/settings).

    Like give us 2 (or more) folders to connect to, rather than one, 1 for the default items (make them read only, but optional?) Then directories for items you write for personal use, then one or more for team shares.

    I share common ones with team, but they don't need my changes, or some I use for personal uses (like formatting code for a book, or snippets for features we don't use)

    Right now, I have started using naming conventions to copy out team items to put into Source Control to share. And then naming standards for tools I am not ready to share.

    This is cumbersome, because then the entire team has to go out and grab the files and put them in their directory in order to not share just that one directory. I personally share my stuff with machines (some of which are not connected to source control), using a dropbox folder.

    Provide an easier way to share SQLPrompt (snippet/code formatting/settings).

    Like give us 2 (or more) folders to connect to, rather than one, 1 for the default items (make them read only, but optional?) Then directories for items you write for personal use, then one or more for team shares.

    I share common ones with team, but they don't need my changes, or some I use for personal uses (like formatting code for a book, or snippets for features we don't use)

    Right now, I have started using naming conventions to copy out team items to put into Source Control to… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Tab History, wrong server

    After doing multiple server migrations, if you open something in tab history that was for one of the previous servers. Sometimes an implicit connection to the server is still used despite not being connected to that server in Object Explorer. This has caused us to have to troubleshoot something that wasn't working anymore when it fact it is just because the connection was the old server. This forces us to copy the SQL statements to Notepad then open a new window and past so that the connection is set to the connected to server. Some kind of warning of this Historical statement is not pointing to the current server connection would be wonderful.

    After doing multiple server migrations, if you open something in tab history that was for one of the previous servers. Sometimes an implicit connection to the server is still used despite not being connected to that server in Object Explorer. This has caused us to have to troubleshoot something that wasn't working anymore when it fact it is just because the connection was the old server. This forces us to copy the SQL statements to Notepad then open a new window and past so that the connection is set to the connected to server. Some kind of warning of this… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Tab history  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Enable tab color for "not connected" tabs

    I would like to set "not connected" tabs to a passive color like light gray to indicate they are not actively connected to a database. Current tab coloring is set by the connection, so this isn't possible. One possible implementation is to create an environment called "not connected" and then specifying NULL in the "SERVER" field.

    This would be especially helpful for those who use SSMS's dark theme with SQL Prompt, because "not connected" tabs become nearly invisible with a black background and black font.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Tab coloring  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Convert IIF to CASE

    We have code littered with IIFs that we would like to convert to CASE. Logically this is straightforward, but achieving it swiftly is proving more difficult. A regex takes care of the simple ones, but the ugly ones with nested functions across multiple lines and all sorts are proving far more difficult.

    Would it be possible to add a feature to SQL Prompt to refactor IIFs into CASE statements? Thanks

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. syntax highlight double quoted column aliases

    SQL prompt doesn't offer a single quote column aliases (which is fine). The code analysis feature says :

    "If aliases are standard identifiers, they do not need delimiters. If they are not, then they should be delimited by double-quotes, not single-quotes."

    what would be good is if SQL prompt had an option within SSMS to highlight double quoted column aliases in another colour (purple perhaps) just to make code more readable... sometimes the sea of black is hard to read when you have long, complex case statements etc.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Name tab with object name when scripting from Object Explorer

    When scripting an object from the Object Explorer, for example with right-click -> Modify or Script as... CREATE To, the tab created has a default name determined by SSMS, for example "SQLQuery45 - database01.sql". It would be great if this naming was the same as when you click F12 on an object name in a script, where the new tab is named the same as the object, for example "dbo.SomeStoredProcedure - database01.sql".

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Script object as alter  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Place space before END when collapsing shorter case statements

    When collapsing CASE expressions shorter then XXX, the END has no space if there is a preceding parenthesis.

    Example1 = CASE t1.Col004 WHEN 1 THEN t1.Col006 END,
    Example1 = CASE t1.Col004 WHEN 1 THEN TRY_CONVERT(int, t1.Col006)END

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. SQL Prompt does not think PERSIST_SAMPLE_PERCENT is valid

    PERSIST_SAMPLE_PERCENT is a new feature in SQL Server 2016 SP1 CU4.

    SQL Prompt does not think this is a valid UPDATE STATISTICS statement:

    UPDATE STATISTICS dbo.MyTable(MyStat)
    WITH FULLSCAN, PERSIST_SAMPLE_PERCENT = ON;

    It is valid and the correct syntax. SQL Prompt should be updated to format this correctly.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. untabify

    When saving/opening file automatically untabify it.

    (select all then edit|advanced|untabify selected lines)

    Some how, some way, despite telling everyone to set convert tabs to spaces we constantly get tabs in our SQL code. It would be really nice to just have it automatically convert to spaces so I can save a few clicks.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Format SQL  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Snowflake

    Please add Prompt features when connecting to a Snowflake database

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Intellisense  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. global temp intellisense

    I use global temp tables (##), and intellisense doesn't pick them up, even after a refresh.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Intellisense  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating