Why is SQL Server 2008 Management Studio Intellisense not working

intellisensesql-server-2008

I'm being driven to insanity trying to figure out why Intellisense just fails to work at all. The server I'm using is local and is 2008, the database is set to 2008 compatibility, Intellisense is on in every menu I can find, and yet no member list will pop up even with a CTRL-J.

Has anyone experienced something like this and found a way to fix it? I really can't bring myself to start work unless I have Intellisense working.

Best Answer

I understand this post is old but if anybody is still searching and has not found a solution to the intellisense issue even after re-installing, applying the cumulative updates, or other methods, then I hope I may be of assistance.

I have Applied SQL 2008 R2 Service Pack 1 which you can download here

http://www.microsoft.com/download/en/details.aspx?id=26727

32 Bit: SQLServer2008R2SP1-KB2528583-x86-ENU.exe

64 Bit: SQLServer2008R2SP1-KB2528583-x64-ENU.exe

I have applied this SP1 and now my intellisense works again. I hope this helps! (:

Related Solutions

Sql-server – How to check if a column exists in a SQL Server table

SQL Server 2005 onwards:

IF EXISTS(SELECT 1 FROM sys.columns 
          WHERE Name = N'columnName'
          AND Object_ID = Object_ID(N'schemaName.tableName'))
BEGIN
    -- Column Exists
END

Martin Smith's version is shorter:

IF COL_LENGTH('schemaName.tableName', 'columnName') IS NOT NULL
BEGIN
    -- Column Exists
END

Sql – Connect different Windows User in SQL Server Management Studio (2005 or later)

While there's no way to connect to multiple servers as different users in a single instance of SSMS, what you're looking for is the following RUNAS syntax:

runas /netonly /user:domain\username program.exe

When you use the "/netonly" switch, you can log in using remote credentials on a domain that you're not currently a member of, even if there's no trust set up. It just tells runas that the credentials will be used for accessing remote resources - the application interacts with the local computer as the currently logged-in user, and interacts with remote computers as the user whose credentials you've given.

You'd still have to run multiple instances of SSMS, but at least you could connect as different windows users in each one.

For example: runas /netonly /user:domain\username ssms.exe

Best Answer

Related Solutions

Sql-server – How to check if a column exists in a SQL Server table

Sql – Connect different Windows User in SQL Server Management Studio (2005 or later)

Related Topic