689 results found

1. drill down drill up from object display

   In SQL Prompt, in the pop-up display for an object, allow drill down from an object reference in the popped-up display.

   In the new feature showing dependencies, implement drill down (from the "uses" section) and drill up (from the "used by" section)

   •  

   •  

   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

2. Surround with, add to the list Select, Pivot, and I am sure there are more items like CTE

   Surround with, add to the list Select, Pivot, and I am sure there are more items like CTE

   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  ·  User interface  ·  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

3. Use formatter to create table of contents

   It would be great to be able to use the formatter to create an automated table of contents based on some recognized commented pattern. For example, I could begin each section of code with:

   --******
   -- Title of section
   --******

   Then after using the formatter it would see the commented section and add the line number for each section in the beginning of the script. I imagine something similar to MS Word's auto generated table of contents.

   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  ·  Format SQL  ·  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

4. Tie the SQL prompt Scripting to SSMS scripting

   IN SSMS there is an entire list of scripting options (turn off/on collation, extended properties, etc). Can SQL Prompt read those options and format the scripts it generates based on those settings?

   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

5. Script as Insert - Floats end up with innacurate data precision

   After running a select on a table with a float(53) column, "Script as INSERT" from the right click menu on the results will script an insert with float(8) as the data type instead of float(53), presumably from the length of the column being recorded as 8 bytes when the float(n) is defined with n being bits.

   Minor thing, but ended up causing issues with an equal statement since the floats had different precision when comparing to the original table.

   https://docs.microsoft.com/en-us/sql/t-sql/data-types/float-and-real-transact-sql?view=sql-server-ver15

   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

6. Fix the confusing multiple usage of your company name

   You should fix the use of multiple versions of your name (Red Gate | Red-Gate | Redgate | redgate | red-gate) across all software and communications. See attached picture.

   We try to promote your products in our consulting company, but everyone uses a different name to refer to your company.

   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  ·  User interface  ·  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. Separate UDF Formating from Built-in in "Function Calls"

   We cannot treat UDF parameter listing/indentation in similar vein to Stored Procedure call formatting. All "Functions", be they UDF or built-in, are lumped into the same four RESTRICTIVE options on the "Function calls" page, and we have no "parentheses style" options for them.

   We need:
   1. Separation by type (UDF vs. Built-in).
   2. Global ==> Parentheses, to apply to UDFs, by our choice.

   Thanks.

   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  ·  Format SQL  ·  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

8. Update process

   Hi, this is not related to SQL Prompt only, but to the update process in general.
   As our company firewall is blocking the link in Help "Check for updates ...", I have to submit the "Download a 28 days trial" form and download the full "SQLToolbelt.exe".
   Which is also blocked by the company proxy rules. :-(
   So I have to download the file on my private PC and then copy it to my business machine.
   I assume, my company is not the only one with such precautionary measures.
   Maybe you can implement additional options to download updates.

   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  ·  User interface  ·  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. Add quotes and commas function with commas before

   Please can the "Add quotes and commas" action conform to the current active style's Commas setting?

   So if the setting is "Place commas before items", then the action should also place the commas before.

   At the moment, I have to run a Format SQL action after using Add quotes and commas, which is cumbersome.

   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  ·  Format SQL  ·  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

10. Add NULL to JOIN suggestions

    When joining two tables, you today get the option to join on known references or identical column names.

    What I would like to see is an extra join option in the suggestions, if both the columns are NULLable:

    SELECT * FROM table1
    INNER JOIN table2 ON (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

    The above example might seem like rubbish at first! But sometimes when you have composite keys, one of the columns in the key might very well be a NULLable value.

    So a more valid example would be:

    SELECT * FROM table1
    INNER JOIN table2 ON table2.comp1 = table1.comp1 AND (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

    When joining two tables, you today get the option to join on known references or identical column names.

    What I would like to see is an extra join option in the suggestions, if both the columns are NULLable:

    SELECT * FROM table1
    INNER JOIN table2 ON (table2.ref1ID = table1.ref1ID OR (table2.ref1ID IS NULL AND table1.ref1ID IS NULL)

    The above example might seem like rubbish at first! But sometimes when you have composite keys, one of the columns in the key might very well be a NULLable value.

    So a more valid example would be:

    SELECT * FROM table1
    INNER JOIN… 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

    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

11. Subquery Column Validation Hint

    There's an obscure coding bug that I've seen multiple times in my 20 years of working with SQL Server, and it can be particularly difficult to spot as it doesn't cause a syntax error, yet the havoc it wreaks can be widespread. Consider the following scenario with two tables; they are similar but have differing column names. Now say I want to insert records from StagingTable into FinalTable, but only if they don't already exist there. Yes, there are other ways to handle this like Merge, Left Outer Join etc., but this is still commonly used and you will no doubt see it in the wild.

    DROP TABLE IF EXISTS dbo.StagingTable;
    CREATE TABLE dbo.StagingTable (Col1 INT, Col2 INT);
    INSERT dbo.StagingTable (Col1, Col2)
    VALUES (1,1), (2,2), (3,3), (4,4);

    DROP TABLE IF EXISTS dbo.FinalTable;
    CREATE TABLE dbo.FinalTable (Int1 INT, Int2 INT);
    INSERT dbo.FinalTable (Int1, Int2)
    VALUES (1,1), (2,2), (3,3);

    --Insert new rows from stagingtable into FinalTable if rows don't already exists there.
    --In this scenario, we should insert 1 row with values (4,4)
    INSERT dbo.FinalTable (Int1, Int2)
    SELECT Col1, Col2
    FROM dbo.StagingTable stg
    WHERE NOT EXISTS (SELECT * FROM dbo.FinalTable WHERE Col1 = stg.Col1)

    --FinalTable still only has three rows, and (4,4) isn't among them.
    SELECT * FROM dbo.FinalTable

    Now, before reading on, run the script above and see if you can figure out why the new row isn't being added.

    In the NOT EXISTS subquery (anti-semi-join), the coder assumed that Col1 exists in FinalTable, but that isn't the case. One might expect this would be cause for a syntax error, but in reality, Col1 DOES exist in the scope of the overall statement, so SQL Server assumes you know what you are doing and executes the query without error, but also without inserting any new data. It's the same as a subquery having a predicate of WHERE 1=1 which of course isn't the desired behavior. The simplest way to avoid this is to ensure that all columns are qualified with table name or alias. When qualified, SQL quickly notices that something is wrong, and points out the error either at parse-time or run-time.

    My suggestion is for SQL Prompt to detect subqueries and call them out IF they use unqualified columns. I'm not suggesting a call-out of missing qualifications in ALL queries as it isn't always required, but by checking subqueries, it might go a long way to preventing this in the future.

    The simple fix to the insert statement above is of course the following:

    INSERT dbo.FinalTable (Int1, Int2)
    SELECT Col1, Col2
    FROM dbo.StagingTable stg
    WHERE NOT EXISTS (SELECT * FROM dbo.FinalTable ft WHERE ft.Int1 = stg.Col1)

    There's an obscure coding bug that I've seen multiple times in my 20 years of working with SQL Server, and it can be particularly difficult to spot as it doesn't cause a syntax error, yet the havoc it wreaks can be widespread. Consider the following scenario with two tables; they are similar but have differing column names. Now say I want to insert records from StagingTable into FinalTable, but only if they don't already exist there. Yes, there are other ways to handle this like Merge, Left Outer Join etc., but this is still commonly used and you will no… 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  ·  Code Analysis  ·  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

12. Shortcut to switch equality statements

    It would be very convenient when going through legacy scripts to be able to hit a shortcut combination to switch the order of an equality statement, for example in a JOIN clause

    For example, with the cursor on "A.ID = User.AccountID":

    SELECT U.Username
    FROM Account AS A
    INNER JOIN Users AS U ON A.ID = U.AccountID AND U.Active = 1
    WHERE A.ID = @AccountID AND U.ID = @UserID

    Becomes
    SELECT U.Username
    FROM Account AS A
    INNER JOIN Users AS U ON U.AccountID = A.ID AND U.Active = 1 --note, only clause where cursor is is switched.
    WHERE A.ID = @AccountID AND U.ID = @UserID

    This would then compliment the casing/qualifying/wildcards/semicolons shortcuts you already have which massively speed up sorting out old queries.

    It would be very convenient when going through legacy scripts to be able to hit a shortcut combination to switch the order of an equality statement, for example in a JOIN clause

    For example, with the cursor on "A.ID = User.AccountID":

    SELECT U.Username
    FROM Account AS A
    INNER JOIN Users AS U ON A.ID = U.AccountID AND U.Active = 1
    WHERE A.ID = @AccountID AND U.ID = @UserID

    Becomes
    SELECT U.Username
    FROM Account AS A
    INNER JOIN Users AS U ON U.AccountID = A.ID AND U.Active = 1 --note, only clause where cursor is is switched.
    WHERE A.ID = @AccountID… 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  ·  User interface  ·  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

13. [RESOLVED] Allow adding screenshots while posting an idea

    Please allow adding images/screenshots while posting an idea. Sometimes it gives a better understanding of the requirement.

    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

14. Fix closing quote for 'N' strings

    When typing a string preceded with 'N' (like N'string value'), when you type the closing quote it gets doubled. Hard to explain, but easy to reproduce. Just type these two statements into SSMS to see the difference:

    SELECT 'Bill' As FirstName
    SELECT N'Bill' As FirstName

    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  ·  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

15. 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

16. 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

17. 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

18. 'Copy as IN clause' orizzontally too

    hi, i'd like to have the function 'Copy as IN clause' not only when i select data vertically but orizzontally too

    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

19. Script as INSERT

    Fix "Script as INSERT" functionality with dates.

    Currently when I use this great functionality all the datetime fields will get a form N'1900-01-01T00.00.00'.

    Unfortunately the Finnish SQL server settings does not recognise that and running this script gives an error "Msg 241, Level 16, State 1, Line 2
    Conversion failed when converting date and/or time from character string.". I have not been able to find a way to change that date format in SQL Prompt Options.

    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

20. backup

    I would like to see intellisense provide you a list of backup devices that are created when you use the backup database key words.

    Backup database [database names in drop down] to [ disk, file, Url, backup devices in dropdown]

    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  ·  Intellisense  ·  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