When is Intellisense going to be supported in SQL Server?
Its painful to program SQL without Intellisense support. Most code has to be checked for bugs at runtime. The experiance is just bad.![]()
I hate it when it tells me syntax error "near" so and so. Why cant it just put a line under the error so I dont have to read the code again and again and again and again and again and forever until i find I missed a "," or something like that.[C]
-
-
Linq videos will help you understand.
SQL projection is before scope. (You say what you want before you say where you want it from) Thus intellisense can misleading. -
this isn't a perfect solution but it works. SQLPrompt from red gate. It is free until they release version 3 then they are charging for version 3. it works with Microsoft Query Analyzer, SQL Server 2005 Management Studio, Visual Studio 2005, Visual Studio .NET 2003, SQL Server 2000 Enterprise Manager, UltraEdit32
-
I wrote a blog post about the beta for Sql Prompt 3. You can read it here...
http://brewder.blogspot.com/2006/12/beta-for-sql-prompt-3-is-now-available.html
One thing to know is that Sql Prompt 3 will only work in Query Analyzer and, I believe, the Sql Server 2005 Manager thingy (I don't have 2005 installed and I don't remember what it's called
).
The product I work on has a fairly large schema and it's a huge productivity gain to be able to just pick tables, fields, etc from a dropdown instead of having to scan the object browser or use sp_help. Now if they could just make it work more like Visual Assist (filter by any part of the name instead of matching just the first part of the name), I would be very happy. -
But I am also not happy that MS went through the integration between SQL and VS 2005, and they forgot the most important thing, which is intellisense. What is the point of having integrated SQL into VS2005, without having the intellisense there?
I want MS to fix this ASAP in Orcas, and maybe they will!
So wait and see. -
Thanks guys.
-
Intellisense for SQL is very hard. Just think about it. You start typing 'SELECT ', how the hell would the editor know what you want to select? It would be a lot easier, if you could just write your source first, like 'FROM ... WHERE ... SELECT ...'. If you've typed 'FROM ...', the editor would know what table(s) you're selecting data from, so Intellisense in the WHERE, ORDER BY, GROUP BY and SELECT would be easy. Even in the FROM and JOIN clauses, Intellisense could be provided. That's why they reversed the order of clauses in C# 3.0.
-
TommyCarlier wrote:Intellisense for SQL is very hard. Just think about it. You start typing 'SELECT ', how the hell would the editor know what you want to select? It would be a lot easier, if you could just write your source first, like 'FROM ... WHERE ... SELECT ...'. If you've typed 'FROM ...', the editor would know what table(s) you're selecting data from, so Intellisense in the WHERE, ORDER BY, GROUP BY and SELECT would be easy. Even in the FROM and JOIN clauses, Intellisense could be provided. That's why they reversed the order of clauses in C# 3.0.
Well, you would not get intellisense support when you start typing select, but you start getting it when you type From. Or the SQL guys have to reorder and change the way we write SQL to be lik LINQ. -
SecretSoftware wrote:Well, you would not get intellisense support when you start typing select, but you start getting it when you type From. Or the SQL guys have to reorder and change the way we write SQL to be lik LINQ.
FROM table
SELECT FirstName, LastName
WHERE Id = @_id
That would be sweet
Unless problems would arise from this? -
TommyCarlier wrote:Intellisense for SQL is very hard. Just think about it. You start typing 'SELECT ', how the hell would the editor know what you want to select? It would be a lot easier, if you could just write your source first, like 'FROM ... WHERE ... SELECT ...'. If you've typed 'FROM ...', the editor would know what table(s) you're selecting data from, so Intellisense in the WHERE, ORDER BY, GROUP BY and SELECT would be easy. Even in the FROM and JOIN clauses, Intellisense could be provided. That's why they reversed the order of clauses in C# 3.0.
Quite weak excuse... Why for guys from SQLPrompt and one more company (I don't remember, some sort of "IDEA") it wasn't SO hard?
-
Yes, I agree too. A company managed to do it, why cant MS do it?
maybe someone from the SQL team care to comment on this? -
I found! Aqua Data Studio
-
Apex Sql Edit has Intellisense and much much more.
This is the absolute best Sql Editor ever.
http://www.apexsql.com/sql_tools_edit.asp -
Disagree...
RegGate ownz with SQL Tools, I have loads of them and they really are the shizznit
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.