643 results found

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

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

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

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

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

6. [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

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

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

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

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

11. '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

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

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

14. Smart Rename on Service Broker Objects

    Smart Rename should work on service broker objects. These objects: Message Types, Contracts, Queues and Services are all interdependent. Renaming Message Types, for example, requires the dropping of the dependent Contracts, which in turn requires the dropping of the dependent Services.
    It would be great to be able to generate the relevant drop and create sql in one hit.

    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

15. Use a cell pattern to format NULL values in "Open in Excel" feature

    When using the feature 'Open in Excel' for grid results, I'm unable to determine in Excel which database values were empty strings vs. NULL values. I like that it no longer exports the word 'NULL', but I'd like some sort of option to be able to make a distinction between the two.

    My idea is to use a cell fill pattern (Format Cells + Fill + Pattern Style), but I would be satisfied with just about anything to be able to make that distinction. The pattern I recommend is the most sparsely dotted option, which shows a tool-tip of 6.25% Gray. That provides both a visual cue and something I can filter on. The filter option shows up for me under "Filter by Color", assuming that the column has more than one pattern in it.

    Edited to add:
    This might be helped or made possible by making a slight, hidden, technical change in how the data is exported to Excel. I noticed that when I run the Excel formula =ISBLANK() on cells that appear blank (in the data set exported by "Open in Excel"), the function returns FALSE. If NULL values could be exported to Excel in a way that allows ISBLANK() to return TRUE, then either you or we could have the option to format blank cells in the data range, allowing us to see the difference between a database NULL vs empty string (''). One way to do that is with VBA code, doing something like the following, where MyRange is an Excel range object of the exported dataset:
    MyRange.SpecialCells(xlCellTypeBlanks).Interior.Pattern = xlPatternGray8

    When using the feature 'Open in Excel' for grid results, I'm unable to determine in Excel which database values were empty strings vs. NULL values. I like that it no longer exports the word 'NULL', but I'd like some sort of option to be able to make a distinction between the two.

    My idea is to use a cell fill pattern (Format Cells + Fill + Pattern Style), but I would be satisfied with just about anything to be able to make that distinction. The pattern I recommend is the most sparsely dotted option, which shows a tool-tip of 6.25%… 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  ·  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

16. improve right click performance

    When I right click in a Stored procedure SSMS hangs, and it takes too long for the menu to show up. Please review Red Gate Source Control for the added entries in the menu to improve performace

    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

17. Add "Set as Active Connection" to Registered Servers

    This is essentially the same as a forgotten SSMS request over here: https://feedback.azure.com/forums/908035/suggestions/32896039

    It would be incredibly useful to be able right-click on a server-node in the Registered Servers list and change/set the connection for the current document window to that. You already have a custom context menu item in there ("Tab Color (Server)", so that hurdle is gone.

    This idea is related to these, but not quite the same. In both cases, it seems they don't know about the Registered Server functionality, so they're basically asking for this idea, plus for you to re-implement that entire feature.
    https://redgate.uservoice.com/forums/94413/suggestions/40385740
    https://redgate.uservoice.com/forums/94413/suggestions/13425135

    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

18. Suggestions window should display CREATE sql for CLR objects

    No CREATE SQL is displayed in the suggestions window when hovering over any CLR objects, or scripting the object as alter. The code returned is just a comment saying:

    -- No creation SQL available for this object type

    The CREATE/ALTER statement can easily be built by querying the relevant system tables. SSMS does it when you script the object and other Redgate products such as SQL Compare and SQL Source Control do it just fine, not sure why SQL Prompt would have been left out.

    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  ·  Script object as alter  ·  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

19. Remove dependance on USE [dbname] in Query window.

    Many time SQL Prompt doesn't work for me because it thinks I use the database mentioned in the last USE statement in the SSMS query window. This is incorrect and confusing since I change the database in the SSMS dropdown without explicit running any USE statement. SQL Prompt should know what database is selected in the dropdown and offer objects from the selected database,

    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

20. Put DISTINCT Keyword At Top of Suggestions List

    Add an option to have the DISTINCT keyword appear at the top of the suggestions list when the first few characters (DIS, DIST) are typed, ahead of any column name suggestions. Nearly every time I type DIS or DIST, I want the DISTINCT keyword and not a column name that begins with the same letters.

    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