Intellisense on some databases, not others??

Question

Post reply

Intellisense on some databases, not others??

December 2, 2024 at 9:14 am

This was removed by the editor as SPAM

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

vikc19 SSC Rookie Points: 31 More actions · Answer 1

Thanks a lot.. Removing the offline linked server worked for me.

erkanbeker Grasshopper Points: 19 More actions · Answer 2

bartedgerton - Thursday, December 4, 2014 1:30 PM
I can tell there is a slight hesitation the first time I type in a query in a new query window at the time when it should be popping up with Intellisense, however, it never does come up with anything, and CTRL-J (list members) has no effect.Of 22 servers, each with a half-dozen or more databases, only this database on 1 server is not allowing Intellisense. I can open up a query window on this server/database and not have Intellisense work, but then use the same query window, but change connection and/or change database, refresh the cache (CTRL-SHIFT-R) and Intellisense works.This wouldn't be such a big deal, but the "1 database" happens to be our main DEV database, where we need it the most (the same database in our TEST and PROD environments does not have the issue!).. in the words of Vizzini.. "Diabolical!"Anyway, the server is fully patched to the latest version, as well as our client machines. Everything has SQL Server 2012 SP2. We are running a mix of developer clients on SSMS 2014 or 2012, and Visual Studio 2010, 2012 and 2013. I even tried to create a VS2012 database project to see if I could "rebuild" the Intellisense cache (no luck, but VS2012 Intellisense works fine for this db).Even after doing a drop and restore from a PROD backup of the same database, Intellisense will not work on the DEV server, but still works fine in TEST and PROD. The other 8 databases on our DEV server have Intellisense working fine.The server environment is a Windows Failover Cluster on 3 servers running Windows Server 2008R2, SQL Server 2012, and the databases in question are in an AlwaysOn Availability Group. The secondary server is read-only, and I can connect to it and it also exhibits the same problem for the same database. The other databases in the same Availability Group are working fine on both Primary and Secondary servers.

I am having the exact same issues with you ? Were you able to solve this issue ?

skitchens Newbie Points: 1 More actions · Answer 3

Created an account just to reply to this post. We had migrated a SQL instance from SQL Server 2012 to 2019 and during the migration, we had set up a link server between the new and the old server to perform some upserts. The link server was set up so that entire catalog was available.

After the migration was done and the old server taken offline, auto complete and intellisense didn't work at all. Didn't matter what version of SSMS, or what type of login, it just didn't work.

Came across this post and checked for any old linked servers...and we still had one. Removed it, and it started working again immediately.

Huge thanks, this was a pain and I couldn't figure out why it would never work.