Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Chris Di LulloSr. IT Pro Marketing Manager Twitter | LinkedIn Pierre Roman Twitter | LinkedIn Mitch Garvis Twitter | LinkedIn Anthony Bartolo Twitter | LinkedIn
Adam Galant is a great guy to know when it comes to Visual Studio Team System… He works in my group in Mississauga on the Developer Tools side of the house and maintains his own blog. I asked him to write up a post specifically about Tem Edition for DB IT Pros in response to a press release and announcment at TechEd next week.
OK, so this isn’t really news now, it’s been about a week, but in case you haven’t heard, we’ve announced the Visual Studio Team Edition for Database Professionals, which is an addition to the Visual Studio Team System role-based products.
Initially targeting SQL 2000 and SQL 2005, it is designed using an extensible architecture that can eventually be used to add support for other database technologies. Interestingly, this tool is intended to bridge a big gap: helping dbas and dbpros integrate better into the software development lifecycle, and helping them with some cool new capabilities. I think this tool will probably become the de-facto tool for anyone doing any work with SQL Server (implementing custom databases).
It is being planned for release later this year (read planned) and will be freely available to folks that have valid and active licenses for Visual Studio Team Suite. Our customers with existing volume licensing agreements may want to step their licenses up to Team Suite before the end of June under a current promotion and save loads of $$ over the estimated retail price.
Some of the things it can do:
More information can be found that the product site at http://msdn.microsoft.com/vstudio/teamsystem/products/dbpro/default.aspx .
I’ll also be throwing more information on my blog around tech*ed 2006 timeframe, as we’ll be putting out a CTP…