Why is IntelliSense not working?

A timely post Aaron.  I am getting the feeling that Intellisense is quickly going down in the "be careful what you wish for" column.

I was going to say that you should be happy if it's not working :-)

There's a space on the end of the link for "When IntelliSense Is Unavailable". Should be this: http://msdn.microsoft.com/en-us/library/ms173434.aspx.

I frequently jump between 2005 and 2008 connections and lose bracket highlighting. I'm anxious to read this link. :)

What..."I was going to say that you should be happy if it's not working :-)"

You people got to be kidding me...

Use Red-Gate SQL Prompt and you will quickly grow to love intellisense...

Just to be able to do "select * from tableA" and have it fill in the names of the columns when I want is worth the price..

So what if intellisense not perfect.. it SAVES a huge amount of time...

-jfc-

Non-working Intellisense--which includes both Microsoft's and Red-Gate's implementations--wastes a lot more time than it saves. Although to be fair to RG, Microsoft's is much worse at this point in terms of getting in the way.

Microsoft's implementation autocompletes with candidates that don't make sense, greatly increasing the number of keystrokes needed in some cases (you need to back out the autocompletion).

RG's does not have that problem, but also doesn't support nearly as much--such as CTEs--and it has bugs where it will occasionally populate the candidate list with incorrect column names. It also often marks perfectly valid SQL as invalid, which does waste time. These comments, by the way, refer to the prerelease version of RG's newest offering in this space.

I hope that some vendor--RG, Microsoft, or other--will solve the Intellisense problem soon. I agree that it would save a lot of time, but the offerings today don't, and for me hurt rather than help my productivity.

One of tools that offer Intellisense for SQL Server 2005 and 2000 is our DbOctopus. Nice thing is it's free until September, so there're no reasons not to give it a shot. It's not just SQL code editor, but you can see that if you visit:

www.cogin.com/dboctopus/

The short story:

grant exec on xp_instance_regread to public

The long story:

We recently upgraded our user testing database to 2008. Intellisense did not work until we tried granting my user SA rights. This prompted us to search for the permission required. The MSDN articles insisted that you will be able to use Intellisense on objects that you have access to, yet I was unable to get Intellisense working on tables I could select from.

I then went to ServerName -> Security -> Logins and tried to view the properties of my login. I got an execute denied error for xp_instance_regread. It turns out that this solves another issue in SSMS 2008 when trying to right click on non-2008 databases. Granting access to this enabled Intellisense.

Peters comments pointed me in the right direction but did not solve my problem.

The issue I found was that I was granted permission to the database server as part of a windows group but my windows login had been added as a user to the database with no role.

I believe this occured during the execution of enterprise library scripts that led to a schema being created with my login name.

When these two items where removed intellisense resumed working.

In summary, check all your permissions are correct before looking elsewhere for a solution

Thank you!

Question: Can EZ-CAP 6.0 handle this? The dilemma is that the member only is added to EZ-CAP once the member has transferred to an IPA Central Health contracts with. But the Healthplan and Option are the same so according to the Healthplan, the benefit accumulators should carry over from the first IPA (that does not contract with Central Health) to the second IPA that does. If Central Health starts the member’s accumulators off at $0 they will not be accurately tracking the member OOP totals and the deductible/OOP maximums will over-charged to the member.

Thanks, this helped to solve an annoying problem I was having :)

Turns out that references to fields for synonyms show up underlined in red also.

I've just upgraded my client tools from 2008 to 2008R2 (connecting to a 2008 R2 server) and there seem to be differences in the implementation of intillisense in Management Studio between the versions.

Pre-upgrade (plain old 2008) to accept a suggestion from autocomplete, you could type either a period, closing square bracket or space, this for me worked pretty well.  

Post upgrade (R2) things are worse, now the period does not accept the suggestion (it instead just appears at the end of what you've typed), the closing square bracket will accept BUT but only if you have NOT started the object name with an opening bracket!! So autocomplete entries end up looking like either dbo]. or [db]

The functionality of the spacebar remains unchanged, but this is annoying if you're autocompleting a db/schema name as you then have to delete the space you've put in, before continuing with the table name.

A shame, I was getting used to autocomplete and it reduces the time taken to get used to a new, complex schema at a client site (I don't have a photgraphic memory and so need either a diagram or something like autocomplete before getting up to speed).

What Dingo said about the period is definitely an annoyance.  I also just upgraded to 2008 R2 and am annoyed at this loss of functionality.

Are there any solutions to this?  I had initially assumed I accidentally disabled that function somehow...why would you take it out?

I used redgate's for years and then changed jobs and am back to microsoft's (which is why I am on this article). I like redgate's a lot but find microsoft's a pain in the rear.

Also it seems they went from a character/case order to a case/character order.  Which makes it all most useless if you are in an environment that has changed their standard for CAPS to camel case.

Example:

TABLECUSTOMER201001

TABLECUSTOMER201002

TABLECUSTOMER201003

TABLECUSTOMER201004

All other CAP TABLES/VIEWS (could be hundreds )

TableCustomer201101

Excellent Aaron!

SSMS 2008 R2 is losing Intellisense after installing Visual Studio 2010 SP1

http://connect.microsoft.com/SQLServer/feedback/details/650569/ssms-2008-r2-is-losing-intellisense-after-installing-visual-studio-2010-sp1

Thx for the post...

I faced the same issue recently & proble resolved by install SQL 2008 SP1

Thx

http://www.mytricks.in/2011/11/fix-sql-server-management-studio.html