How can we improve SQL Prompt?

Load suggestions from sql files in Visual Studio/SSDT Projects

Prompt currently needs a database connection to retrieve objects/suggestions from, which it gets from a database project's "Target Connection String".

It would be better if prompt loaded suggestions directly from the sql files in the project without needing the database.

66 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Aaron LawAdminAaron Law (Software Engineer, Redgate) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        I just reinstalled prompt and updated my licence so that I could use it in visual studio now that we are moving to that over SMSS and cannot believe this isn't included. What a useless tool for visual studio, I shouldn't have to have a dev database in sync with my SSDT project just to be able use prompt..

      • Anonymous commented  ·   ·  Flag as inappropriate

        As a join dev / production DBA I work in Visual Studio a lot of time, and I am seriously thinking of removing SqlPrompt from SSMS so I don't have different add ons in the two tools. You are losing lots of people with feet in the development camp by not supporting VS/SSDT projects. (I appreciate you may have you own continuous development options / routes but I am in a team using TFS / Visual Studio driven by C# coding and they need TFS/Visual Studio so cannot swap but I probably could get them over them over to SQL Prompt if it was supported properly in VS)

      • ChrisChris commented  ·   ·  Flag as inappropriate

        Red Gate, you are losing .Net developers using this product because of the lack of integration to the project!

      • SergeySergey commented  ·   ·  Flag as inappropriate

        Tried a trial version of SQL Prompt 7 with Visual Studio 2015 and looks like it is almost useless without proper SSDT integration - I have to re-deploy the project anytime I make changes to its schema in order to see those changes in IntelliSense.

      • Andre LightAndre Light commented  ·   ·  Flag as inappropriate

        One other thing: I find myself turning off SQL Prompt regularly because it gets in the way of SSDT IntelliSense, which actually works on changes made to the local project without having to sync to the database first. If Redgate doesn't add more robust SSDT support, they're likely going to lose Visual Studio users.

      • Andre LightAndre Light commented  ·   ·  Flag as inappropriate

        Now that I have SSDT, I rarely use SSMS because SSDT enables me to keep my entire solution, including the database, in one place. It also is a much more advanced development environment than SSMS (including the text editor), allows finding/updating code and DB references using a single Find/Replace, etc. Because of that, you can be sure that any developer using Visual Studio is soon going to migrate from using SSMS to using SSDT most of the time.

      Feedback and Knowledge Base