Comments (7)

  1. DimitrisV says:

    Euan,

    well it is not officially supported but you should know that WSS SP2 supports ASP.NET v2.

    Because I am working on big project with the Reporting Services of SQL 2005 and Sharepoint I tried the WSS SP2 and it worked (with SQL 2005 CTP) lovely.

    So when I saw that the release of SPS SP2 advertised the support of APS.NET v2, I gave it a shot, applying all the knowledge I got at the PDC 😉

    So I pressumed that the only way the things can be messed up was the support on the framework and nowhere else. And it works.

    I have to tell you that before the homepage of the portal used to take quite a few seconds to open. Now it takes splits of seconds.

  2. DimitrisV says:

    Oh my G*d!

    Just realized that you are a Program Manager at the SQL Team! Cant believe the honour.

    But more so I just cant believe why you cant believe the lovely work that you have put on SQL 2005. Well done lads!

    (Just take care of that tiny bug with the Reporting Services Installation on non-english locales before RTM, OK ? as well as that other litle nuisance when you add a new report on a project 😉 )

    Also I have to say one more tiny complain. We were looking forward to the intellitype of SQL, we know it is hard but thought it not impossible.

    Keep up the good work. If you like, send me a profile for a test and I will perform it on my servers for you to give you a report back.

  3. euanga says:

    There are several options for intellisense for SQL Server.

    You can add support into Query Analyzer, Management Studio or Visual Studio vis the folks at http://www.promptsql.com. I will however point out that they are not using a published API for this work so if it causes system instability etc there is not much we can do to help.

    You can also buy a variety of editors out there that have have intellisense support, Apex SQL, Embarcadero and Quest spring to mind.

  4. PromptSQL does its stuff using standard Windows calls — low level system hooks, Windows API, .NET class library etc.

    No code-injection, or undocumented API calls etc. Just a normal .NET program running in separate process.

    Regards,

    Damian (PromptSQL developer)

    "I will however point out that they are not using a published API for this work so if it causes system instability etc there is not much we can do to help."

  5. euanga says:

    I should be clear, QA, SSMS and VS were not designed or tested to be extended this way, by calls from outside the process.

  6. Neither was UltraEdit :-)

    http://www.promptsql.com/is_demos/UltraEdit32.gif

    Your point is well taken — its tricky to make PromptSQL look like its part of QA, when its not – sometimes the cracks show. Hopefully not too often.