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

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.

46 results found

  1. Improve keyboard support

    I click "New Data Comparison" (or "New Schema Comparison"), then ALT-W to open the "Database Connection Properties" dialog, then TAB to get into the "Server" input box. Once there, I type a part of the name of the server and the list of available servers works nicely!

    It seems that I must use down DOWN ARROW to select the server from the list and press ENTER before I can get out.

    However, if I type the entire server name, I can't get out of that box! Pressing TAB or ENTER does nothing.

    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…)
    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

  2. Increase UI response and overal performance (SQL Data Compare)

    Opening windows takes much time.
    I believe the most often used features must work as fast as possible to provide the best experience (including not only processing but opening windows).
    See how long it takes to open "New Data Comparison" and moving through tabs "Source and Target", "Options", "Mapping".
    The app itself opens slowly as well opening "dcomp"-files.

    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…)
    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

  3. Search does not find all objects

    Search does not find all stored procedures in a case sensitive database. The default case insensitive search misses some objects. To make it work, you must specify the exact case sensitive search string and make the search case sensitive. The default server collation in my instance was case insensitive.

    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…)
    0 comments  ·  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

  4. Save breakpoint information when closing a query

    If you set a breakpoint, then close the query, when you open the query back up, the previously set breakpoint is no longer present.

    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…)
    0 comments  ·  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

  5. enable

    Window headings are only sql, sql1, sql2 an not the name of the datatable.

    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…)
    0 comments  ·  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. Data Editor should be case sensitive when determining whether to update

    When a value is changed in the Data Editor, the Data Editor logic compares the value with the existing value and makes a decision whether to update the existing value based on whether the new value is considered different. Currently, this equality comparison is case insensitive, which is a bug. It must be case sensitive. SSMS will update data based upon consideration for case sensitivity, but not the Data Editor.

    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…)
    0 comments  ·  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
1 3 Next →
  • Don't see your idea?