The Journey to Katmai

  • Comments posted here are about the content posted at http://www.sqlservercentral.com/columnists/sjones/3044.asp

  • I would like to install the 2k8 ctp on a vista machine; I have already a 2k5 developer (named) instance installed. I've read that the 2k8 ctp does not work yet with many instances; can I install it as a 2nd instance on this machine? I would not want to break the sql 2k5 installation. Thank you in advance.

     

  • The following side-by-side conditions are not supported in this release:

    • Side-by-side Tools - Presence of SQL Server 2005 Management Tools or BI Development Studio will block installation of SQL Server "Katmai" Management Tools and BI Development Studio.
    • Side-by-side with SQL Server 2000 - An instance of SQL Server 2000, including MSDE, will block installation of this release of SQL Server "Katmai".
    • Side-by-side with SQL Server "Katmai" CTP1 - An instance of SQL Server "Katmai" CTP1 will block installation of this release of SQL Server "Katmai".
    • Side-by-side instances of SQL Server "Katmai" CTP3 - Multiple instances of this release of SQL Server "Katmai" are not supported on a single computer.

    This is from BOL of SQL 2008.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • Thank you. It's great to know.

  • I'm actually pretty excited about the baked in spatial support in Katmai.

    http://www.directionsmag.com/article.php?article_id=2477&trv=1

  • Consider using virtual server's - install a virtual server, andd then on the cirtual server you *should* be able to install Katmai

    anyone doing this yet? I'm waiting to get virtual server on a machine that can handle it...

  • Here's a bit of trivia - Katmai was Intel's code name for the original Pentium III processor. You'd think that somebody at MS would have known that

  • I have always wanted Microsoft to incorporate an ability to see who are the active users and the complete sql they are running as Oracle enterprise manager lets you do(more information than sp_who2 provides)

    Mike

  • In SQL 2000, use the function ::fn_get_sql (X'sqh handle') where SQL_handle is the sql_handle column from sysprocesses.

    In SQL 2005, have a look at sys.dm_exec_sql_text(sql_handle), getting sql_handle from sys.sysprocesses

    HTH

  • Intellisense would be nice, but only if they incorporate it into Visual Studio too. I have to believe the majority of SQL developers use VS and not EM/SSMS.

    I also think Red-Gate has missed a golden opportunity by having SQL Prompt only hocked into SSMS. From what I've read, it was a challenge for them, since SSMS doesn't expose a plug-in architecture. VS already exposes this architecture, so you would think it would be fairly easy for them to adapt their existing SQL Prompt code over to VS.

    I could be wrong and perhaps that's one of the reasons Red-Gate is publishing this software and I'm not.

    Thoughts ?

    Thanks,

    Don

  • Hi Don,

    Actually we'll be adding support for Visual Studio 2005 in the next version that will be out in July. SSMS is based on VS 2005 so exposes many of the same VSIP interfaces although due to some seemingly minor omissions plugging into it is less straightforward than VS. On the other hand Visual Studio presents its own complexities since it uses a different SQL editor, so for example it's not as easy to get at the database connection properties as it is in SSMS or Query Analyzer.

    We are still hoping to get an early access release of the new version of SQL Prompt out within the next week or so, however we're having installer issues at the moment due to bundling all of our installers into one uber-installer so it's possible that may not happen. If that's the case the first publicly available release will be the RC, which should be available in the middle of July.

    The reason we didn't put Visual Studio support into the 3.0/3.1 releases was simply that our market research in the run-up to kicking off the 3.0 project indicated that 90% of people used SSMS or Query Analyzer as their primary editor, and VS 2005 came in with about 5% of the vote. Subsequently we've had a lot of people ask for the VS support, which isn't surprising given that we ran our survey over a year ago so you'd expect many more people to have adopted VS 2005 by now, so we've added it in this new release.

    I should also point out that this will be a free upgrade for anyone who's already purchased SQL Prompt 3.0/3.1.

    Hope that helps.

    Thanks,

    Bart

  • Hi Bart,

    Thanks for the extended reply. Once again you're showing how Red-Gate is focus on delivering customer satisfaction and it's one of the main reasons I continue to recommend the purchase of your products within our company.

    I do tons more development work writing SP's then I do one or two line of DBA tasks, so VS really comes in handy for me.

    I know you guys already have a great testing team, but if you need someone outside the company to give it a spin, feel free to send it my way.

    I don't mean to be too pushy, but ... any change of getting SQL Refactoring integrated into VS too ?

    Thanks again and keep up the good work,

    Don

  • Hi Don,

    I can't really speak for SQL Refactor, however what I can say is that it would be more complex to integrate into VS because there are more points of contact between it and SSMS, notably in the object tree, than with SQL Prompt, so we'd need to find ways to replicate all of that in VS. Unfortunately I can't really give you any indication of when the next version of SQL Refactor might appear, however I have asked the relevant people here so I'm happy to post more when I know more.

    I apologise because that doesn't really help much right now. What I would say is if you want to make some noise about this then the best place to do so is the SQL Refactor support forum:

    http://www.red-gate.com/MessageBoard/viewforum.php?f=53

    Much of our product development, at least where existing products are concerned, is based directly on customer feedback, so the more people ask for something the more likely it is to get done, and the sooner it's likely to get done.

    Thanks,

    Bart

  • Same here! We have around 200gig +/- in ArcInfo databases, I think the new spatial support will add some very cool capability but it's going to be a whole lot of learning! People start slinging ESRI slang around me and it might as well be Greek.

    Plus, we're not going to 2005, so 2008 will almost be a requirement (after the first SP). Everything we have now is in 2000.

    -----
    [font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]

  • In response again mainly to Don. If you're after SQL intellisense in Visual Studio 2005 you can give the SQL Prompt 3.5 release candidate a whirl. This is now available at:

    ftp://ftp.red-gate.com/sqlpromptbeta/SQLPrompt3.5.0.000323.exe

    There are also a whole raft of other improvements, such as cross-database support. These are all listed on my blog, not that I'm that much of a blogger, but I will be posting some more detailed information about all the new stuff later:

    http://www.simple-talk.com/community/blogs/bart/default.aspx

    The current post is pretty much a verbatim copy of my post on the Red Gate support forums.

    Enjoy!

    Thanks,

    Bart

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply