So SSIS 2008 packages must be deployed to SQL 2008 environments SSIS 2012 packages to SQL 2012, etc. For whatever reason, the SQL team coupled their design tool versions with the SQL server run-time environment. While you can develop SSRS reports in SSDT 2012 and deploy them to SQL 2008 (or R2) environments, you cannot do the same with SSIS and SSAS packages. With the release of SQL 2012, the product team packaged a new version of BIDS, dubbed SQL Server Data Tools 2012 (which runs on the VS 2010 shell – confused yet?). SQL 2008 R2 is technically only one generation behind the latest release, yet it relies on the VS 2008 shell for Business Intelligence development (such as SQL Reporting Services, SSIS and SSAS projects). As in Business Intelligence Development Studio, the VS 2008 Shell that ships with SQL 2008 and SQL 2008 R2. Yes, Visual Studio 2008 is a three-generation-behind product and, with Visual Studio’s multi-targeting support, upgrading the IDE has become increasingly trivial. In general, I’m happy to see Microsoft deprecating support of three-generation-behind products – I was elated when they dropped VS 2005 support in TFS 2012 – but this time the reaction was mixed.
This configuration supports users in accessing Team Foundation version control from these earlier client versions.
#Sql server business intelligence development studio 2013 code#
To connect to Visual Studio Team Foundation Server 2013 from Visual Studio 2008 or Team Explorer for Visual Studio 2005 Team System requires installation of Microsoft Source Code Control Interface (MSSCCI) Provider 2013. Of note this time around was the deprecated support of Visual Studio 2008. With the release of TFS 2013 (huzzah!) came another round of regression testing where I work.
0 kommentar(er)
