We really need is, or the option to use VS SSDT intellisense when no suggestions come from SQL Prompt

Current interest. Please implement!

Visual Studio has built in Intellisense that can check across the database project files.

However when installing SQL prompt this overwrites this functionality.
I would have expected SQL prompt to be complimentary and not take over.

As the Code analysis is very good and can help people that work in projects.

Working in a project doesn't always mean the objects are deployed immediately to the database. So SQL prompt becomes counter intuitive within VS.

I think this needs to be re worked to make it complimentary to VS functionality

This just made my decision to spend the extra money on DB Forge SQL Complete.

This feature would be a significant relief in the development of database projects. Are there any efforts to implement the point after all?

Still no news on this one?

In my opinion this is expected behaviour, it defeats the purpose of using it Visual Studio otherwise.

This feature would be great. The only thing I really wish for the next release.

Doesn't appear to be a "lack of interest". This is number two in the Top Ideas.

I'm surprised that Redgate dropped it.
IMHO SSDT will be used more and more in the future.

As a passionate SQL Prompt user in SSMS, I'm missing this for SSDT Database projects!

Dear SQL Prompt team, we've been waiting this feature for years, please don't drop it. I'll very surprised that none of your competitors have implemented it yet.

I don't think that there is a lack of interest as this feature is absolutely critical for your product, probably users are tired of waiting for it to be implemented as original idea was shared 4 years ago. It is the only reason why my development department isn't considering buying a SQL Prompt license.

Adding my voice. Support for SSDT projects is still important. SQL Prompt is useless to me without it. I realize SSDT is a competing product with the Redgate suite but not having SSDT support isn't going to convert my company to use the rest of the Redgate suite; it's just going to have us not bother with SQL Prompt.

Now that SQL Prompt is built into VS 2017 I'm surprised this isn't higher priority. I think the people who would find this most useful are the ones that haven't had SQL Prompt previously and they won't see why they should enable it because it really doesn't do much while you're developing database solutions. Any changes you make to schema in a VS solution aren't picked up by SQL Prompt so developers are not seeing how great a piece of software it is.

Inline with Gert Hauan comments, without this feature using SQL Prompt with Visual Studio just doesnt work for development. I was told this feature was coming over 12 months ago, my renewal for SQL Prompt has come and gone because this feature has not been added.

OK, so here is a comment just so we can have some action on the task. This is something that really makes SQL Prompt worthless in Visual Studio. As others have commented, I have had to turn off SQL Prompt in SSDT-projects to at least get Visual studios own intellisense. Please don't take this off your radar. Why won't you do it? Is it to complex?

SQL Prompt needs to be able to view the database project's compiled objects to pull from instead of from a live sql server. For me, it's pretty useless without that.

I'm not a fan of SSDT, but looks like more and more developers are moving to it.

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..

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)