Sdílet prostřednictvím

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

  • Článek

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: https://www.microsoft.com/en-us/download/details.aspx?id=42313.

Comments

  • Anonymous
    April 02, 2014
    Any chance of turning any of those red dots green?
  • Anonymous
    April 02, 2014
    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?
  • Anonymous
    April 02, 2014
    Is this only available as a 32bit Version; I can't add the Features to a 64bit instance (Enterprise Edition)
  • Anonymous
    April 02, 2014
    I'm with Paul, what are the chances of compatibility with SQL Server 2012 SP1 for SSIS please?
  • Anonymous
    April 02, 2014
    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.
  • Anonymous
    April 02, 2014
    SSIS SQL 2012 support, PLEASE!
  • Anonymous
    April 03, 2014
    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.  
  • Anonymous
    April 03, 2014
    @ 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.  
  • Anonymous
    April 03, 2014
    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?
  • Anonymous
    April 04, 2014
    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?
  • Anonymous
    April 04, 2014
    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/sqlserverKasper
  • Anonymous
    April 04, 2014
    "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?
  • Anonymous
    April 06, 2014
    How come SQL Server Database Template is not included in this? How do i install it?
  • Anonymous
    April 07, 2014
    Wow - that was pretty quick! I won't ask what branch it came from :). Congrats!
  • Anonymous
    April 07, 2014
    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.
  • Anonymous
    April 08, 2014
    It works on SQL Server 2008 Reporting Services?
  • Anonymous
    April 10, 2014
    The comment has been removed
  • Anonymous
    April 11, 2014
    Any idea when this will be re-released?  Trying to get a SQL 2014 demo database up. Loading sample data in using the "import data" wizard or sql bulk loading is frustrating, to say the least.
  • Anonymous
    April 14, 2014
    When will this be working again? Killed migration to VS2013 dead in its tracks.
  • Anonymous
    April 17, 2014
    Any ETA on when it will be available again? Finally started migrating to VS2013 and now dead in the water again...
  • Anonymous
    April 17, 2014
    It has been more than a week now... do we know when this tool will be available again?  If this product was managed like Azure or Office, it would be fixed by now.  
  • Anonymous
    April 17, 2014
    Does anyone know if the CTP2 version of SSDT-BI will work with the full release of SQL 2014? We're taking considerable heat for not being able to make the switch to 2014/VS 2013 by this weekend. We'll take anything to get us moving, even if it's a bit glitchy.
  • Anonymous
    April 17, 2014
    @Eric   We've identified a fix to the issue and expect the update out soon.  I hesitate to give out dates since there might be a slip.  But, we're talking about a week at this point.
  • Anonymous
    April 23, 2014
    Agreed. VS 2013 for BI is a real pain. We are in SQL 2012 (BI) and not moving anytime soon: Not enough added value for Corporate BI in SQL 2014. (As stated by some other post, there is absolutely NOTHING new in SSIS, SSRS or SSAS)
  • Anonymous
    April 25, 2014
    The comment has been removed
  • Anonymous
    April 26, 2014
    Couple of weeks is really a long time for such as issue that can be avoided in the first place. SSDT-BI has always been issues people complained about for the last 2-3 versions due to bad coordination between VS Team and SQL Team.
  • Anonymous
    April 28, 2014
    @Iced Tea - entirely agreed. And what's worse is they only selectively publish comments on these blogs, so you're likely only seeing half of the complaints.This is all happening at a point in time when my own organization is reconsidering our business intelligence strategy from the ground up. I'd like it to include SSAS, SSIS, and SSRS - but MS has been making it a very hard sell.
  • Anonymous
    April 29, 2014
    The comment has been removed
  • Anonymous
    April 29, 2014
    Does the VS 2012 SSDT-BI package released in February work with SQL Server 2014?  While it would be nice to have VS 2013 package I just need something that works with SQL Server 2014 to do some cube design right now.
  • Anonymous
    April 29, 2014
    Wonder when they will get the Report Viewer to print in Chrome and drop ActiveX?   The Report Builder 3 for Sql Server 2014 won't install either.
  • Anonymous
    May 04, 2014
    Any news on this?
  • Anonymous
    May 07, 2014
    Any update on this?  Is anyone even reading this stuff?  "A few more days" is now approaching a month.
  • Anonymous
    May 07, 2014
    We have had some technical delays but we’re still  actively working on it.
  • Anonymous
    May 08, 2014
    Please can MS communicate an accurate time for this?  A few days != 5 weeks !  Basic courtesy kindly requested :)
  • Anonymous
    May 12, 2014
    I am hopeful that they are taking the time to complete the SSIS 2012,2008 compatibility...
  • Anonymous
    May 13, 2014
    The comment has been removed
  • Anonymous
    May 13, 2014
    It has been more than a month now. The VS team even had time to ship VS 2013 update 2.Why is SSDT-BI taking so long?  
  • Anonymous
    May 13, 2014
    We apologize for the delay and the inconvenience to all of you. We are working round-the-clock on this and aim to release it in the next week or two.
  • Anonymous
    May 14, 2014
    Any news on this? SQL 2014 has been out for a while already so my expectation is that these tools should have been released by now?
  • Anonymous
    May 14, 2014
    Status update?  It's been over a month.  Generally, a few days < a month.  Thoughts?
  • Anonymous
    May 14, 2014
    The comment has been removed
  • Anonymous
    May 15, 2014
    Hmmmm....   "aim to release it in the next week or two." ???Let's see... "a few more days" turned into a month.   That means " next week or two" should equal about 5 months?Come on, SSDT-BI team.   This is unfortunately not the first time the BI tools have lagged behind SQL and VS releases.   Can you please do what it takes to get tooling releases coordinated in the future?   And if not, maybe work on better communication with your customers?   Maybe ask the VS / Azure teams for some advice.   They seem to be doing things right these days.
  • Anonymous
    May 19, 2014
    I only have Visual Studio 2013 and need to build SSRS 2012 reports. How long are we going to have to wait? Is there any place to get the version that was recalled?
  • Anonymous
    May 19, 2014
    Could we shoot for Q2 2015?  Kidding
  • Anonymous
    May 20, 2014
    Seems the blog comments are just as easy for them to ignore as all the bugs and feedback submitted on connect...
  • Anonymous
    May 22, 2014
    Can we get an update on ETA for release?
  • Anonymous
    May 23, 2014
    New version for visual studio 2013 is now available.
  • Anonymous
    May 24, 2014
    After installation of new release, just try to New projet, Import from Tabular server... New BI SSDT is unable to open a database where name is different from ID...
  • Anonymous
    May 25, 2014
    Hi, I am not able to repro this issue on my machine. Can you file a bug on connect.microsoft.com/sqlserver so we can take a look.Thanks,Kasper
  • Anonymous
    May 25, 2014
    Is it possible to have SSDT-BI for VS.NET 2013 installed parallel to SSDT-BI for VS.NET 2012? I won't be able to migrate everything at once.
  • Anonymous
    May 26, 2014
    Have I missed something? I thought the next update was going to allow us to use SSDT-BI on Visual Studio 2013 and author SSIS packages for SQL 2012 (in other words, add some backwards compatibility)? I have installed the update from 23 May and I don't see that option... Any comments?
  • Anonymous
    May 26, 2014
    After installing the new release opening a 2012 SSIS project in VS 2013 starts the conversion to SQL 2014 format wizard.We all like to play with new technology but I think for most production environments SQL 2014 is a long way off getting rolled out so we really need to ability to develop & maintain SQL 2012 BI projects using VS 2013 rather than having to install multiple IDE's etc.
  • Anonymous
    May 27, 2014
    As I think these comments are currently being read by Microsoft.  In case you haven't picked up on the message, VS2013 SSIS packages for SQL 2012 is a mandatory requirement for the majority of your customers.  If you want the new tooling to be used, this must be provided.  Your customers are tired of being forced to use multiple versions of the IDE.You say you have fixed the code so this 2014 code will provide 2014 compatibility when you release SQL.VNext, but your customers need SQL 2012 support in this VS2013 product.  This is a much larger deal than the "few days" bug fix taking more than a month.It is time to provide for your customers needs.
  • Anonymous
    May 27, 2014
    Thanks for your feedback on SSIS, I have send it to the SSIS team.Thx,Kasper
  • Anonymous
    May 27, 2014
    The comment has been removed
  • Anonymous
    May 27, 2014
    to answer John, I've had similar issues when working with SSDT BI and Visual Studio 2012 and 2013. The problem seems to be more with the way that the shared folders are (not) handled during the uninstall/reinstall process. I was only able to do a reinstall successfully after uninstalling all Visual Studio releases (including the shell) and going through and manually removing anything related to VS or SQL Server in the %AppData%/Microsoft folders (and their Local equivalents - %AppData% points to the Roaming folder). You may also have to go through and clean some registry settings.This experience prompted me to talk to our LAN team about looking at getting my team some virtual machines to use instead of losing so many man hours.
  • Anonymous
    May 28, 2014
    @Lars-Erik: yes SSDT-BI for VS2013/SQL2014 can be installed side by side with SSDT-BI for VS2012/SQL2012.
  • Anonymous
    May 28, 2014
    The comment has been removed
  • Anonymous
    May 28, 2014
    @Samuel Jones: Thanks for the advice Samuel. I will try another round of uninstalls, taking more care to delete everything manually this time and see if it works.
  • Anonymous
    May 28, 2014
    @John Bosch, we have tried for some time today but we have not been able to reproduce your issue with the latest download. Can you please open a connect item (connect.microsoft.com/SQLServer) so that we can contact you for further details?
  • Anonymous
    May 29, 2014
    The comment has been removed
  • Anonymous
    June 09, 2014
    Any chance of turning any of those red dots green?
  • Anonymous
    June 10, 2014
    Where is the SSDT-BI Visual Studio 2012 for SQL Server 2014?
  • Anonymous
    June 10, 2014
    Great to see this released!  Unfortunately, it fails to install - "The CPU architecture of installing feature(s) is different than then instance specified.  To continue, add features to this instance with the same architecture".  Of course, that message is nonsense as I'm only attempting to add shared features, not instance-specific features, and there's only 1 architecture of the shared features - X86.Any ideas?
  • Anonymous
    June 10, 2014
    @Hog, SSIS team is already planning on that improvement but there isn't a concrete release date so far.
  • Anonymous
    June 10, 2014
    According to icons I have locally SQL Server Express 2012, Visual Studio 2012 and SQL Server Data Tools 2012. More exactly I have SQL Management Tool, SSIS and SSRS of version 2014.  All should be 64 bit versions as well as JDK.I wish to make an SSAS project and everything works well until I try to deploy it locally.But then it says "Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems :  A connection cannot be made. Ensure that the server is running.  To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server."I have recreated connections a few times and I can't find anything wrong in them.Configuration Manager says that SQL Server and SSRS are running. I don't have SSAS on the list, should I have it?I tried to add SSAS by installing SQL Server 2014, but it refuses to add anything and according to help this is because everything is installed already.Do I need to remove SQL Server 2012 and after that to install 2014 or do I have something else wrong?
  • Anonymous
    June 10, 2014
    CarID,I think I have seen the same issue as you describe and I think it is to do with what is selected during the install by default which is add new features to an existing instance and breaks if this is 64bit, change this to new instance or whatever the option is and it should install the tools.
  • Anonymous
    June 11, 2014
    I have Win 8.1 Pro VM with SSDT-BI for VS 2013. It was installed prior to "pull out" (1st week of April 2014). Could that initial release still be used? OR if I have to install this latest/re-released version, what are my options?a) Uninstall all relevant stuff of SSDT-BI for VS 2013 listed in "Programs and Features", and try (re)install latest release?b) Rebuild Win 8.1 Pro VM and then have fresh install of SSDT-BI for VS 2013 latest release?Thank you for your time & help.
  • Anonymous
    June 12, 2014
    The comment has been removed
  • Anonymous
    June 15, 2014
    Is there a SSDT-BI specific forum ? I try to script the partitions in a SSAS project, however so far didn't find a way to do that so I can use it in the deployment. The gui approach is ok for hobby projects, however for real enterprise work it is not usable.
  • Anonymous
    June 16, 2014
    SSIS 2012 support in VS 2013 would be great guys
  • Anonymous
    June 17, 2014
    Does Xiaoning Ding's comment of June 10 indicate that VS2012 support of SSIS 2012 is somewhere on the timeline? I have the "opportunity" to move from svn to TFS, and I'm having trouble deciding which version to install...
  • Anonymous
    September 07, 2016
    Thɑnkѕ very nicce blog!