SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI)

SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI)

Rate This
  • Comments 72

Yesterday we released SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI) for SQL Server 2014.  With this release you can use SSDT BI in Visual Studio 2013 and it includes the Visual Studio Project Templates for Analysis Services, Integration Services, and Reporting Services.  The project templates in this release generally work with down level versions of the server (with the exception of SSIS).  See the image below for details. 

We have also retired the CTP version that was based on VS 2012.

SSDT-BI for Visual Studio 2013 has been re-released in English. It can be downloaded from: http://www.microsoft.com/en-us/download/details.aspx?id=42313.

 

  • Any chance of turning any of those red dots green?

  • I have SQL Server Express 2014 x64 installed on my machine. When I want to install the Business Intelligence SSDT package it wants to install a new x86 instance of SQL Server Express. Setup will stop with an error if I tell it to add the Features to the existing x64 SQL instance. Any ideas?

  • Is this only available as a 32bit Version; I can't add the Features to a 64bit instance (Enterprise Edition)

  • I'm with Paul, what are the chances of compatibility with SQL Server 2012 SP1 for SSIS please?

  • After reviewing it I have to apologize for my question :)

    SSDT is only available in x86, which is fine. As it only consists of Shared Features, you simply have to select "Create new instance ..." in the Installation wizard. The Features of course can't be added to a 64bit instance as there's no need to...

    @Hassi: This also applies to your question.

  • SSIS SQL 2012 support, PLEASE!

  • SSDT-BI is only available in 32 bit because Visual Studio is only available in 32 bit.  It can work with 64 bit processes (as external out of proc dlls) but is limited to 32 bit because of VS.  

  • @ Paul.  The red dots are representative of the way that SSIS has worked for years.  They typically only support the current server.  However, the SSIS team has put the mechanism in place for this release that will enable them to support down level versions as well.  For this release it means those red dots stay the same.  However, future releases will have more green dots.  

  • So  if I have av Sql Server 2012 SSIS server, I can deploy but NOT run a SSDT BI project made in Visual Studio 2013? If so when will this be fixed?

  • I think the confusing thing here is that Books Online says "SQL Server 2014 Integration Services is unchanged from the previous release."...yet for some reason we can't use SSDT BI 2014 to create solutions for the "previous release" (2012). Anyone care to explain what's going on?

  • This behavior has been there for many releases for SSIS, SSIS only allows you to deploy to the same version as you have installed. The fix has been made that going forward this is not an issue any more. I have passed this feedback on to the SSIS folks (we are the SSAS team). A better way to give feedback is to file a suggestion / bug on connect. connect.microsoft.com/sqlserver

    Kasper

  • "For this release it means those red dots stay the same.  However, future releases will have more green dots."

    Does that mean there will be more green dots for future releases of SSDT-BI 2014 for VS 2013, or are you referring to future major updates of SQL Server (for example from 2012 to 2014)? In other words, is there a chance SSDT-BI 2014 for VS 2013 might be compatible with SQL Server 2012 SSIS in the future?

  • How come SQL Server Database Template is not included in this? How do i install it?

  • Wow - that was pretty quick! I won't ask what branch it came from :). Congrats!

  • I've actually been holding back moving our data team off of VS 2008 hoping their SSIS would work for this.  Looks like we're stuck on VS 2012 though unless there is a planned patch to include SSIS support for SQL 2012?  We just upgraded to SQL 2012 so SQL 2014 is probably a few years away if not skipped for the latest at that time.

Page 1 of 5 (72 items) 12345