Skip to content

SQL Prompt

Welcome to the SQL Prompt feature suggestion list. Find out more information about SQL Prompt at http://www.red-gate.com/products/sql-development/sql-prompt/.

If you have any questions, need help or have found a bug in SQL Prompt, please visit the forums or our support portal.

SQL Prompt

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

10 results found

  1. There is no Smart Rename option for User Defined Table Types. This should be implemented.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. when i join 2 tables with columns having same name sql raise the error 'Ambiguous column name'. if it possible i think it is usefull to have an auto alias generator. example:
    select a.name, b.name from a join b => select a.name as aname, b.name as bname

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Smart rename doesn't work on Azure SQL Database without creating a SQL login to use for the task. Be nice to support connections via Active Directory Password, or any of the other Azure AD auth options.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would be incredibly useful to have Smart Rename have the option to generate a synonym that points the old name to the new one, in order to maintain functionality for any legacy applications accessing the database via those old object names.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. When one would like to smart rename a column, the smart rename function does not update a MERGE statement. Could this be added to the smart rename feature?

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. sometimes I need to just change the casing of letters in a field name (e.g. a field has GUID and I want to make it Guid). smart rename does not allow me to change the name if the new name is exactly the same saying that a column with this name already exists.

    so I change the name to GuidXXXX and then on the generated script remove the XXXX and the script runs just fine.

    I think smart rename should not warn that the name exists if I am just changing casing of the name

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Self explanatory... Need to right-click a user-defined schema and be able to generate a script that effects the scema rename and code within all affected objects. Would be great to add a list of additional databases in which to look for candidate objects to change: triggers, SPs, UDFs...

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Enhance Smart Rename to accept a list of name changes.

    Even if it runs the existing smart rename and concatenates the scripts it would save a lot of data entry time versus doing each change one at a time.

    You should require fully qualified names in the import data to avoid ambiguity errors.

    57 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’re going to be reviewing this over the next couple of months, which would be released via the SQL Prompt for Teams EAP (get in touch if you want to know more).

    In the meantime please add any other information that you think would be useful.

  • Don't see your idea?