Information, tips, news and announcements about SQL Server Analysis Services and PowerPivot directly from the product team.
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.
Can we get an update on ETA for release?
New version for visual studio 2013 is now available.
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...
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.
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.
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?
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.
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.
Thanks for your feedback on SSIS, I have send it to the SSIS team.
After installing these BI tools none of my existing database projects will open in VS2012 nor VS2013. All fail with the error "Failed to create extension manager for the target platform 'Microsoft.Data.Tools.Schema.Sql.Sql110DatabaseSchemaProvider'". Creating a new database project in Visual Studio 2012 leaves me with an error box stating "Failed to create extension manager for the target platform 'Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider'".
I have uninstalled and re-installed SQL Server 2012, VS2012 and VS2013 and all associated Data Tool and BI Tool packs, not including this one. Nothing works and I am now facing doing a complete system refresh (a restore did not fix things). Something I am seriously loath to do.
Can anybody suggest what may have gone wrong and an easier solution that a complete refresh (which I'm not even convinced will work)?
I am a very angry customer right now!
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.
@Lars-Erik: yes SSDT-BI for VS2013/SQL2014 can be installed side by side with SSDT-BI for VS2012/SQL2012.
@Craig, Brian, Randy:
This SSDT-BI refresh (uploaded last Friday) was only to fix the existing bugs. It didn’t include new feature improvements.
Regarding the support for SSIS 2012, we really appreciate your feedback and we understand its importance. Actually SSIS team has started working on this project. It’s not an easy work because we need to make sure it’s compatible with existing SSIS 2012 third-party extensions. I will share more information once we have a firm date when the SSDT-BI for VS2013 refresh will include this improvement.
@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.
@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?