Skip to content
← Customer Feedback for Devart

dbForge Studio for SQL Server

dbForge Studio for SQL Server is an SQL server development tool incorporating query builder, data import/export and compare tools for managing and analyzing data.

To consider your idea as soon as possible, follow the guidelines:
  • Describe the goal you want to achieve and what result you want to get
  • If you have a solution, add it to the description
  • Give examples that we can use to implement your ideas
  • Add one suggestion per post. If you have several ideas, share them in separate posts
  • Add comments to the suggestion

dbForge Studio for SQL Server

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve the product?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

9 results found

  1. Find results highlighted on scrollbar

    In SSMS, when you search for a term, all locations of that term are highlighted on the scrollbar, making it easy to navigate to the locations of that term and to know where they appear in the file. In dbForge Studio, you can bookmark all, but that requires you to scroll through the entire document to find all instances and does not provide a complete picture of all of the places the term appears.

    This is a very important feature that is missing for me as I rely on that heavily in SSMS. I would like to see similar functionality…

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Excel-Export without explicit formatting

    The Excel-export shouldn't necessarily put explicit formatting on the cells. That it does is annoying as it forces one to explicitly remove it again before the data can be formatted as a table with one of the Excel table format templates, for instance. Another example is that although number fields are actually marked as being number fields, they are still displayed as left aligned, because that's how they are explicitly (and wrongly) formatted.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. On the customer License Information page, add a user editable field where we can log who has which license.

    I purchase the licenses for my dev team, so when I purchase two licenses, one for myself (SQL Tools) and a separate on for one of my devs (Schema Compare) I would like to indicate which is assigned to whom. Currently on the License information page, both appear assigned to me. While two folks is easy, if we grow our usage of your products further, I would like to know who I've assigned which licenses to, while keeping them all under the one account.

    All I'm looking for is a field that I as the customer can note this type…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. history

    Please move the Clear button for Query History from the main UI screen to be in the Options menu. In context, it seems like it is going to clear the search filters rather than wiping out the entire query history. It does warn you - but the history is so useful and important. Clearing it out should be a harder, more explicit step than just clicking twice. Not that I've done that... Multiple times...

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Schema added to properties when not required

    Currently when I use Query designer the resulting query is expressed as:

    SELECT
  Hygiene360Log.Hygiene360LogId,
  Hygiene360Log.RequestDate
FROM dbo.Hygiene360Log

    Where what I want is the minimum length of text to correctly identify tables and objects, like this:

    SELECT
  Hygiene360LogId,
  RequestDate
FROM Hygiene360Log

    It's very annoying

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Bugs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. pin tab

    how is possible there is no simple thing as pin tabs?

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. remote changes source control

    For source control (GIT) at the remote changes tab add a ignore/delete option.

    I started working with the database and deleted/renamed some stored procedures. When I detached and attached my source control (GIT) it wants to add the procedures which I have removed.
    This is fine when someone else changed it, but now I specifically want to delete this procedures. When working with this I can add them again, to delete them afterwards, or I can delete them in the folder and check them in with GIT, bypassing dbForge.

    The easy solution would be to add a ignore/delete/keep local option…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Detach stored SQL query from SQL connection

    At present, if I developed a SQL query, stored it and try to load it back into dbForge at a later date, dbForge 'remembers' the SQL connection it is associated with and tries to connect automatically. I want to be able to disable this behaviour via options - eg opening file does NOT try to be clever.

    EXTENDED RATIONALE

    In common usage, the feature is quite useful. Unfortunately, in some of the projects I am working with, I have to constantly switch between different environments (prod, pre-prod, demo, devops, etc) protected by external VPN. All environments are hosting the same…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Set Compatibility Level to SQL 2022 (160) on Edit Database Page

    Right click on a database on a SQL Server 2022 Enterprise Edition Instance and select Edit Database. Switch to the Options tab. Select the Compatibility level dropdown, I am only seeing up to SQL Server 2019 (150) as options, I am missing the SQL Server 2022 (160) option and need to manually write the ALTER DATABASE statement to set it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Bugs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?