IntelliSense is not working in SQL Server Management Studio

74,478

Solution 1

You can try solution from these questions1 or questions2 and questions3.
Or please try these steps as below:

  • Enable IntelliSense:
    • For all query windows, please go to Tools >> Options >> Text Editor >> Transact-SQL >> IntelliSense, and select Enable IntelliSense.
    • For each opening query window, please go to Query >> Intellisense Enabled.
  • Enable statement completion: please go to Tools >> Options >> Text Editor >> Transact-SQL >> General, and check on Auto list members and Parameter information boxes.
  • Refresh IntelliSense local cache: please go to >> Edit >> IntelliSense >>Refresh Local Cache or use the CTRL+Shift+R keyboard shortcut to refresh.
  • Wait a minute or two for the Refresh to finish before trying again.

Solution 2

I had the same issue. Everything was enabled to ensure proper Intellisense functions, but didn't work. I realized I had SQLCMD mode enabled by default. Disabling it restored Intellisense functionality :)

Solution 3

This may seem too short of an answer, but probably it's the solution to your Problem:

CTRL+SHIFT+R

Also, I found this: Troubleshooting IntelliSense (SQL Server Management Studio)

Solution 4

Increasing the Maximum script size under Tools, Options, Text Editor, Transact-SQL, IntelliSense fixed Intellisense for me.

Solution 5

Missing from other solutions, but fixed it for me:

Edit > IntelliSense > Toggle Completion Mode

or CTRL+ALT+Space

Share:
74,478
Ethem Kuloglu
Author by

Ethem Kuloglu

a .Net developer...

Updated on November 12, 2020

Comments

  • Ethem Kuloglu
    Ethem Kuloglu over 3 years

    We use SQL Server Management Studio 2008 R2. IntelliSense works with SA account perfectly. But it is not working with Windows Authentication user. The user has access master db with db_owner role but it's not sysadmin.

    How do I fix this issue?

  • Ethem Kuloglu
    Ethem Kuloglu almost 9 years
    not working again. Everything is fine when loged in as SA. But other user(not sysadmin) cant use this feature.
  • KarmaEDV
    KarmaEDV almost 7 years
    Depending on the size and schema of the DB it can last several minutes until IntelliSense is populated
  • JoeT
    JoeT about 6 years
    That got it working. Strange. I set Maximum Script Size to 2 MB from 1 MB. Then I set back from 2MB back to original of 1MB and it's still working. That's odd as you'd expect it to stop working.
  • Shaji
    Shaji over 5 years
    I tried a million things before I stumbled upon this post. Really appreciate it. Intellisense worked on 2012 as soon as I unchecked sqlcmd.
  • FAB
    FAB about 5 years
    Thanks for this suggestion. Although the option was already on, my intellisense did not work until the typical "turn it off and on again"...
  • Dunc
    Dunc about 5 years
    FYI, this is the keyboard shortcut for Edit > IntelliSense > Refresh Local Cache. Some of the other options in that menu may help, if this doesn't (I just tried them all).
  • Kayathiri
    Kayathiri over 4 years
    Thx a lot. I was struggling with this for a day.
  • Moshe Yalovsky
    Moshe Yalovsky almost 4 years
    Changing the Maximum script size fixed it for me too. Everything else was set correctly!
  • serge
    serge over 3 years
    also, ensure you are connected! I didn't manage intellisense to work, because took a yesterday launched query window, and MSSMS was already disconnected. Once reconnected the intellisense worked! )
  • esp
    esp over 3 years
    Finally I have intellisense again - Enable statement completion was missing for me
  • JonV
    JonV about 3 years
    This was the fix for me as well. I found that I needed to turn it on - and then OFF again (2X? I don't remember now).
  • Andy Brown
    Andy Brown over 2 years
    I had to turn SQLCMD mode off for all new queries (Tools > Options > Query Execution > SQL Server > General), then for some reason I needed to leave SSMS and go back in. Yeah - I have my Intellisense back!
  • Josh B
    Josh B over 2 years
    To my amazement, this fixed the issue for me too.