Code Insight?

IIRC Code Insight is borlands name for Intellisense (and a bunch more stuff)

Definitely. I think SSMS was a huge improvement over Enterprise Manager and Query Analyzer, still i tend using ApexSQL Edit instead, and there are two reasons:

Code Completion (Intellisense)

Code Snipplets (lets you actually lookup data in the database when you use it)

You do know that Intellisense were present in one of the really early betas in SQL Server 2005?

I'm hooking on to this one.

When you type FROM <space> you should have a list containing:

A) Schemas defined in the sql script file

B) Selectable objects (tables, views, ctes, synonyms and functions returning record set) from script file

C) Schemas defined in the database in the current database

D) Selectable objects (tables, views, ctes, synonyms and functions returning record set) from the current database

E) The name of any database from which you can select.

As you type, objects not matching the typed text should be removed.

WHEN you go back to select columns, you should see:

A) All columns available from all sources in the from clause

B) All common functions

C) All user-defined functions from the script file

D) All user-defined functions from the current database context

This sounds very heavy, but keep in mind... The information may be cached in the app...

That's good news Balaji. Thanks a lot.

Just feedback about the problems we have with current products that offer intellisense for SQL:

• Need to enable it or disable it easily. Very long scripts (i.e. scripting an entire db) make all Intellisense product go buts, slow and un-useful.
• When switching between multiple large db, it becomes dreadful (trying to load the schema of a db with thousands of objects can't be anything else than long).
• Scripts that refer to multiple dbs are also a problem (server.db.schema.name).
• Being able to limit the tool to tables/views, etc. could be useful. If I am working on the schema I don't want it to load, parse and understand all dependancies in stored procedures. That could give a nice speed boost.
• Products usually go nuts with complex scripts (lots of corrolated sub-queries, CTE, etc.). Two things that would help are:
  • recommend users to terminated statements with ';' to help the parser. This is a good practice anyway now because it is required in some cases (CTEs)
  • provide a visual cue as to was the "current statement" is. Any typo can make the parser behave differently. I know VS does this already but SSMS does not (and VS is NOT a dba tool. I use VS for C# work and will always use SSMS for dba work).
• We also work with SQL 2005 Compact. Since we also open Compact dbs with SSMS, the Intellisense feature usually turns belly up. If it can't work with SQL Server 2005 Compact, it should at least ignore it.

Hope it helps