LEFT OUTER JOIN sys.system_sql_modules AS ssmsp

WHEN ISNULL(finition, finition) IS NULL THEN 1 SELECT SCHEMA_NAME(sp.schema_id) AS ,ĪND name = N'microsoft_database_tools_support'

I recently noticed asynch_network_io waits shoot up, and it appears that the cause is increased usage of intellisense…or there is something wrong. What I'm still trying to figure out, though, is why there is a SQL Server 2005 version of the page, since IntelliSense does not exist in Management Studio for 2005, nor does it work in 2008 against 2005 instances. So many thanks for this document Alan, as I think it will help others as well. I was also unaware, until today, that Alan Brewer at Microsoft created a Books Online page that documents these and other cases: Little did I know, there are a number of other situations where IntelliSense will not function correctly (e.g.

SQL Server 2005), where IntelliSense does not function (see Connect #341872 from Whitney Weaver for more info and LOTS of community feedback on this decision :-)). The query window is connected to a downlevel server (e.g.You can fix this easily by going to Edit > IntelliSense > Refresh Local Cache, or CTRL+SHIFT+R. The object is not in the local IntelliSense cache, since it was created recently.Most of the time, it is for one of two reasons: I see people complain that IntelliSense (new in SQL Server 2008's Management Studio) is not working.

Visual studio reset intellisense cache