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.

4 results found

  1. Invalid colimn add scripting for new columns

    If new colums have a sparse they will be scrithed without.
    At second syng diff can be detected and scripted as :
    ALTER TABLE [dbo].[lalala]
    ALTER
    COLUMN [lala] ADD SPARSE
    GO
    IF @@ERROR<>0 OR @@TRANCOUNT=0 BEGIN IF @@TRANCOUNT>0 ROLLBACK SET NOEXEC ON END
    GO

    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…)
    declined  ·  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. Autocomplete not working if more than 1 query

    In an Sql window, if I type:

    select Field1 from Table1

    ... autocomplete works ok (i.e. Field1 and Table1 will appear as suggestions). However, if in the same window I type:

    select Field1 from Table1
    select Field2 from Table2

    ... Autocomplete doesn't work for the second line of sql. It only seems to work for the query which is at the top of the sql window.

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

  3. selected stored proc execution script is deselected after execution

    1. in SQL Editor, execute selected stored proc e.g. declare @p1 nvarchar(4000) set @p1=NULL declare @p4 xml set @p4=convert(xml,N'<paramData></paramData>') exec api.widgetpreferencesave select @p1
    2. after execution (multiple recordset returned), the selected code has been deselected
    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…)
    declined  ·  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. Strange Cursor Behaviour

    The cursor sometimes displays as a bar, but in the wrong place - i.e. you can be typing somewhere else. Or the bar becomes stuck, and the cursor where you're typing becomes a small vertical rectangle - and it all doesn't quite work correctly.
    This ambiguity over where the cursor really is, coupled with the (very nice) F8 feature, is quite dangerous: you could easily think you're going to execute one statement, when actually you will execute a quite different statement.

    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…)
    declined  ·  2 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
  • Don't see your idea?