With 2016, SSMS is now free, and the installer for it is separate from the installer for the SQL Server server components (Database Engine, Integration Services, etc.).Plus, Microsoft is now releasing updates and improvements for it on a roughly monthly basis.This problem is really proving to be a tricky one (and quite annoying).Is there anything else i can do to fix this problem? As @Erik mentioned, Intellisense is not perfect at picking up changes made to the database since the script was first opened or created.
I checked the obvious: Troubleshooting Intelli Sense (SQL Server Management Studio) reconfirmed what I already knew and didn't help. This is not a duplicate because while other forum posts list the above steps as "answers" they are not answers for me.They do not solve the problem of intermittent Intelli Sense. It's unpredictable but frequent enough to hamper productivity.Our remote SQL Server was recently upgraded to 2014.I installed SQL Server Management Studio 2014 on my Windows 10 client computer. Suppose I'm typing The moment I type the period, I expect Intelli Sense to list the available tables, as it always does.
The cache is refreshed asynchronously in another session.
It sounds like two separate intellisense behaviors are perhaps being discussed in the comments. The discussion is around refreshing the cache in the case of schema changes, but "not working" could also just mean the intellisense dialog intermittently doesn't appear at all when it should. It's still supported to use it against SQL Server 2014 (in fact, it's supported to use it against instances as old as SQL Server 2008).