Skip to content

SQL Complete

dbForge SQL Complete is an intellisense add-in for SQL Server Management Studio and Visual Studio with advanced autocompletion and formatting features of T-SQL code.

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

http://www.devart.com/dbforge/sql/sqlcomplete/

SQL Complete

Categories

JUMP TO ANOTHER FORUM

3 results found

  1. When searching in execution history, the search value is used pretty quickly after you stop typing. This means that you have to wait for the search to finish even if you weren't done typing the search string. It also means that if you have a typo, you have to wait for the search to finish before you can correct it. I keep a long history of executed SQL, so each search takes a while to run.

    In my opinion, it would be better to have a dedicated "Search" button so that you could submit your search string when you're finished…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  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)
  2. New option to Toggle commenting/uncommenting on the current line selections as most other editors have. Map to CONTROL-/ by default to match the commenting behavior of other editors.

    Why SSMS does not have this baked in is f'in ponderous.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 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)
  3. In our schema, we have the unfortunate convention (if you can call it that...) of including underscores in many table and sproc names. For instance, a report sproc might be named ReportSalesByChannel. It would be awesome if the CamelCase interpretation either completely ignored the underscores in the name while providing the suggestions (so typing rsbc would suggest the above named report), or make it so the _ is one of the interpreted characters, which would allow rsbc to again suggest the above sproc. Right now any stored procedure with an underscore cannot be quickly suggested by any abbreviation…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 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)
  • Don't see your idea?