Intellisense doesn't work in some servers

Naomi 7,366 Reputation points
2022-10-28T20:43:43.68+00:00

Hi everybody,

I'm connecting to several servers. For some Intellisense and SQL Prompt work fine, but for some Intellisense doesn't work at all and it's very frustrating. I'm connecting using VPN. What may affect Intellisense on some servers (including local SQL Server Express installation where it doesn't work), but not others?

Thanks in advance.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,139 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 104.3K Reputation points MVP
    2022-10-28T21:13:55.483+00:00

    Here a list of things from the top of my head that prevents Intellisense from working:

    -- SQL 2005 and older.
    -- Someone has revoked access to the catalog views to public.
    -- Server/database is in single-user mode.
    -- You have connected on the admin connection. (a.k.a. the DAC.)

    I never run into this myself of the simple reason that I detest intellinonsense, and always turn it off.

    0 comments No comments

  2. PandaPan-MSFT 1,906 Reputation points
    2022-10-31T05:56:38.46+00:00

    Hi @Naomi ,
    I wanna add some possible reasons that may make IntelliSense not work:

    1.The local cache used by IntelliSense becomes stale. You can go to Edit -> IntelliSense -> Refresh Local Cache

    2.This way maybe a little bit complicated but pls take some time to check if the IntelliSense was set as enabled:
    Go to Tools -> Options -> Text Editor -> Transact-SQL -> General -> IntelliSense
    Go to Query -> IntelliSense should be selected
    Also verify that the T-SQL Editor does not launch in SQLCMD Mode. To check:
    Go to Tools -> Options -> Query Execution -> SQL Server -> General
    Make sure "By default, open new queries in SQLCMD mode" is unchecked.
    or Go to Query -> SQLCMD Mode should not be selected

    3.There is bug that VS2010 may cause this problem. Pls check this link: kb2531482-%E4%BF%AE%E5%A4%8D-%E5%AE%89%E8%A3%85-visual-studio-2010-sp1-%E5%90%8E-ssms-2008-r2-%E4%B8%AD%E7%9A%84%E6%99%BA%E8%83%BD%E6%84%9F%E7%9F%A5%E5%8A%9F%E8%83%BD%E5%8F%AF%E8%83%BD%E4%BC%9A%E5%81%9C%E6%AD%A2%E8%BF%90%E8%A1%8C-c4f0c486-918d-fc10-cbdb-587e20d0e355

    4.Pls check this official link (some possbile reasons are shown on it) : https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/ks1ka3t6(v=vs.90)?redirectedfrom=MSDN


    If the answer is helpful,  please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"

    0 comments No comments