That’s pretty basic, but to someone who doesn’t know what they’re doing, that could be good for a start.I’ll stop demonstrating the native SQL Server Intellisense now, because unfortunately there really isn’t much more to show.Initially I tried Tools - General and checked if ‘Auto List Members’ and ‘Parameter Information’ was enabled (which it was). This caused Intellisense to stop working, but this was just after I had installed Code Rush.See the article Code Rush Stops Intellisense Working For Visual Studio 2013 for more.As a result, I would like to explain the reasons why SQL Prompt makes me decide to turn native intellisense OFF.I don’t want to merely promote Red Gate tools: Instead, I want to show you how this tool improves my work, and also suggest some new ideas to the Red Gate developers (who have already seen this article).
It literally worked the one minute, and stopped working the next.These aren’t criticisms, but rather to suggest possible ways that would make the tool even more indispensable to people like me.If you’ve not heard about SQL Prompt before, I really do recommend that you download the trial version and take it for a spin.While this isn’t a critical bug as some would like to believe, it is a bit frustrating.
Luckily it is easily solved and not the end of the world as we know it. I recently experienced the same issue on Visual Studio 2013.I also love T-SQL, and IÂ´m lucky to work in a company which uses a lot of stored procs, functions etc., and so SQL Server Management Studio is my home, the place where I feel comfortable.