July 1, 2009 at 5:01 am
can anybody tell me how to add intellisense in sqlserver2k5 without purchasing it......Needed to add it manually............
tanx
seetha
July 1, 2009 at 7:03 am
The only way I know is buying something like SQLPrompt (Redgate). There's no built-in intellisense in SQL 2005 and the intellisense built into SQL 2008 only works when connected to a SQL 2008 server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2009 at 7:27 am
GilaMonster (7/1/2009)
The only way I know is buying something like SQLPrompt (Redgate). There's no built-in intellisense in SQL 2005 and the intellisense built into SQL 2008 only works when connected to a SQL 2008 server.
Which brings up some questions:
1. What difference does it make what version a server is on for Intellisense to work?
2. Does anyone else find Intellisense getting in your way, hindering you more than helping you? I ended up turning it off - too ofter it would automatically fill in wrong words for me. If you're typing your code without actively watching the screen, then it becomes easy. For instance, if typing
declare @var xml
I'll end up with:
declare @var xmlnamespaces (or something like that)
IMO, a great idea (works great in VS), but it just gets in my way in SSMS more than it helps me.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
July 1, 2009 at 7:35 am
I too found it to be kind of sketchy in SSMS, where it was screwing me much more often than helping, I too shut it off. I had similar issues in VS, but to a lesser degree..
CEWII
July 1, 2009 at 7:40 am
You can find many applications that can do intellisense for SQL Server 2005 even for SQL Serve 2000! - But sure that you should buy it!
😎
July 1, 2009 at 7:42 am
WayneS (7/1/2009)
Which brings up some questions:1. What difference does it make what version a server is on for Intellisense to work?
Valid T-SQL constructs. Should intellisense show that DATE is a valid data type or not? Should it show that TRUNCATE_ONLY is a valid clause for backup log or not? The answer to both depends on what version the engine that I'm connected to is.
Design decision was to only support native intellisense when connected to SLQ 2008 servers. In the earlier CTPs, it worked regardless but validated only SQL 2008 syntax (so date was shown as a valid data type)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2009 at 8:26 am
GilaMonster (7/1/2009)
WayneS (7/1/2009)
Which brings up some questions:1. What difference does it make what version a server is on for Intellisense to work?
Valid T-SQL constructs.
Good point Gail. So much of what I do is pretty much the same between 05/08 that I hadn't considered it. Thanks.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply