April 11, 2011 | SQL Server

Connect Digest : 2011-04-11

This week I decided to focus on some of the long-outstanding issues with IntelliSense in Management Studio. While I know many of you are using 3rd party tools like RedGate's SQL Prompt, not everybody has that luxury – in my case, I can't justify a license for every single server I touch, since I can't connect to every environment using SSMS remotely. While I like the idea of IntelliSense, it gets in my way more than it helps, so I always disable the feature.

#650569 : SSMS 2008 R2 is losing Intellisense after installing Visual Studio 2010 SP1 – Daniel Schmitz

#614130 : Intellisense doesn't work with CAST – Simon Sabin

#552093 : SSMS : IntelliSense still has some gaping holes – Me

#578186 : SSMS : IntelliSense for DDL Triggers is incomplete – Me

#330118 : SSMS : some words syntax highlight when they should not – Me

#566786 : SSMS: Intellisense breaks when a database is taken offline – Joel Searcy

#518243 : SSMS : IntelliSense doesn't quite have OBJECTPROPERTY right – Me

#331633 : SSMS : IntelliSense does not recognize synonyms – Me

#478568 : SSMS Gets Blocked and Locks Up During Index Creation – Adam Machanic

#311948 : IntelliSense does not complete the names of some functions – Razvan Socol

2 comments on this post

    • jonmcrawford - April 12, 2011, 4:59 PM

      Are you using SSMS Tools Pack? I have SQL Prompt at work, and SSMS Tools Pack at home, well worth the (zero) money šŸ˜‰ (Thanks Mladen, by the way)

    • JReeves - April 13, 2011, 9:22 PM

      Have you tried SQL Assistant?  Cheaper (licensed per developer) and faster than the SQL Prompt I used to use. (just disable history, it's annoying)

Comments are closed.