IntelliSense 在 SQL Server Management Studio 中不工作

Question

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?

Answer 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.

Answer 2

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)

Answer 3

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 :)

Answer 4

增加工具、选项、文本编辑器、Transact-SQL、IntelliSense 下的最大脚本大小为我修复了 Intellisense。

Answer 5

Missing from other solutions, but fixed it for me:

Edit > IntelliSense > Toggle Completion Mode

or CTRL+ALT+Space

Answer 6

Turning Query > SQLCMD Mode on and off again fixed the issue for me in SSMS 18.1, even though it was never enabled to begin with.

After trying all the answers here to no avail and giving up, I remained curious about the SQLCMD Mode mentioned in Chow Lover's answer. I turned it on to see what it did, but noticed no change so turned it off again. Intellisense suddenly awoke and has been working fine since.

Answer 7

My schemes were too big. I had to do this:

Tools >> Options >> Text Editor >> Transact-SQL >> Intellisence

Maximum script size: Unlimited

Answer 8

I tried all the above/below suggestions... and nothing worked.

• Going to options and toggling everything off and on didn't work .
• Toggling SQLCMD didn't work
• Going to Edit > Intellisense and toggling everything off and on didn't work .
• Changing RAM and Cache size didn't work .
• I tried rebooting and that didn't work .

But the one thing that finally (in an act of desparation where I'd try anything ... even the stupidest idea ever suggested...) that finally... DID WORK was:

I opened a new query tab. Copied my code from the script file I had open, Pasted it into the new query tab. And proceeded to be stunned in horror as intellisense began working again.

Not only did it begin working in my new query tab... but it began working in my original one as well.

Sometimes I just want to bang my head againt the desk.

Hope this tid bit helps someone. :)

PS Yes... I waited a while after each of the failed attempts to make sure intellisense wasn't taking it's good ole time trying to find itself. The "New Query Tab" insanity worked instantly.

Answer 9

I fixed this in 2 simple steps:

1. Go to Tools > Options > Text Editor > Transact-SQL > IntelliSense , tick everything and setup the settings this way:

2. Go to Query > SQLCMD Mode , and disable that:

Answer 10

Issue:

My SSMS Intellisense was not working. Intellisense was Enabled from the Tools. Refreshed the Intellisense Local cache and still no luck.

Solution:

For me, the solution was to increase SQL Server Minimum memory per query y (in KB). It was set to 1024 KB(1M). I increased it to 100 MB then it solved my problem.

Disclaimer Notice:

Please do not make this kind of changes without consulting your DBA and not knowing the resources available on that server. It basically, will allocate that amount of space for every new query window you will open. So, if you set too many users then you have low memory server and you set to something higher then your server might crash .

Minimum memory per query settings:

Answer 11

I found solution at the end. I installed SQL2008 R2 SP3.

Answer 12

It could also depends on your destination server.

For instance for server 2005, intellisense will not work. Here is a command to check this :

SELECT SERVERPROPERTY('ProductVersion');

If version begin with 8 or 9 it will not work .

More information for : sql server intellisense trouble here

A workaround could be to use a sql server plugin as Autocomplete version express

Answer 13

安装visual studio或升级之后，这个问题可能会发生，请点击以下链接： sqI ntelliSense中的IntelliSense问题是什么，为了解决这个问题，您可以这样做：通过更新到最新版本来更新sql server ，您可以获得您的解决方案。

Answer 14

• if Auto list members and Parameter information boxes are ENABLE, make them disable and then press ok button. After the operation, make the boxes enable again and press ok button.
• if Auto list members and Parameter information boxes are DISABLE, make them enable and then press ok button.

Answer 15

If you have are seeing your text in red color, and have a bunch of statements, it could be because of a missing quote. Or a bad syntax check. Try typing a quote at the end. Then Intellisense should kick in again in your next statement.

Answer 16

This is what works for me almost every time when intellisense goes off. I go to the top of the query that I'm working on, and type:

Use DatabaseName; 
go

in SQL Server Management Studio, highlight it, and hit F5 (replace name of database with whichever one you are working on right now). When that has actioned, press Ctrl-shift-R, and then wait for around 30 seconds (maximum should be 2 mins). Intellisense should restart and make intelligent suggestions once again (assuming you are in the same query window as your F5 kick above).

You're welcome, mine is a pint of cider.

Answer 17

Disabling / re-enabling IntelliSense worked for me:

Tools > Options > Text Editor > Transact-SQL > IntelliSense > Enable IntelliSense

Answer 18

Something else that I'd like to add, when all of the above responses don't fix the issue. I've noticed in SSMS that if there is a syntax error that intellisense sometimes doesn't work.

A quick /* */ around the block of code will usually take care of it.

I hope this helps someone.

Answer 19

I just had a problem with one particular database. Other databases on the same instance were fine. I tried refreshing local cache (Ctrl+Shift+R) and disabling and enabling IntelliSense via Tools --> Options, but enabling and then disabling SQLCMD Mode appeared to do the trick for me. Perhaps it was a combination of these things.