I've got VS2015 installed and the latest version of SQL Server Data Tools installed and can't seem to import a circa 2008 SSRS reporting project.
Or even create a new reporting project for that matter.
Can someone point me in the right direction?
Zack
As of Sep 14, 2015 Sql Server Reporting Services (SSRS) hasn't been released as part of SSDT 2015.
Link to the page.
One of the positive news from SSDT Preview update for August 2015 is now there will be only one installer for database and BI tools. No more SSDT naming confusion which was introduced with SQL Server 2012.
For now you have to install SSDT-BI-2013 or SSDT-BI-2012.
SSDT is updated on July 7 2016, can be downloaded from Microsoft website https://msdn.microsoft.com/en-us/library/mt204009.aspx
Related
we have SQL Server 2012 and Visual Studio 2013.
I needed to install BIDS (or SSDT) for developing reports.
I downloaded and installed Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=42313
However during the installation I noticed that it runs SQL Server 2014 setup.
Why doesnt it ask for wich SQL Server version I need SSDT to be installed?
Will it work with SQL Server 2012?
Thanks.
If you use Visual Studio 2015 + SSDT, you will have a full backwards compatible version of the BI toolset (2012 and up for SSIS, 2008 and up for other SSAS/SSRS and the relational DB tools). For previous versions of the BI suite, these were tied to specific SQL Server versions:
SSDT-BI for VS2013 -> SQL Server 2014 support
SSDT-BI for VS2012 -> SQL Server 2012 support
BIDS -> SQL Server 2008 support
The current recommendation is to use Visual Studio 2015 + SSDT as it receives regular updates & bug fixes, and is backwards compatible with no need to map to a specific SQL Server version. You can download SSDT here.
Visual Studio 2015 is now supported as well for dotConnect. The setup file SetupODTforVS2015.exe was released in Oct 2015 (download here). I'm using oracle version 8.4 and Visual Studio 2015 and would like to get Oracle Developer Tools. The installation didn't show any errors, but afterwards no change visible - still not working. Has someone experience with ODT for VS 2015 or does anyone know if oracle 8.4 is incompatible? Thx in advance.
I found the answer in the devart forum:
With Visual Studio 2015 you need to use dotConnect for Oracle 8.4.422
or higher or to compile license resources manually.
I was using minor Version 8.4.225.0.
Seems as if there's no way around compiling licences manually or upgrading dotConnect.
Which order should these be installed in? I have read in this SO post that VS2013 requires an update to work with SQL Server 2014.
It doesn't matter. The two products do not conflict and side-by-side installation is supported in any order.
After installing VS you'll need to then install the latest SSDT version for SQL Server 2014 support. SSDT is s component of Visual Studio, not SQL Server.
I might be slow or something but I can only find RU1 to CRM 2013. Where can I find the upgrade (not a full installer) to lift from 2013 to 2015? I've got one since before but after some confusion and a case of "too many cooks in the kitchen", it claims that it can't perform.
Where do I get the official upgrade from 2013 to 2015?
(Yes, I've googled for it. I get a lot but not the actual binaries from MS.)
To upgrade from CRM 2013 to CRM 2015 you need to install Service Pack 1 on the CRM 2013 server. Then, there are three options to do an upgrade, which is describet in the Implementation Guide for CRM 2015 and in short consists of the following steps:
In-place upgrade, pop the 2015 installation media on the existing server and run it.
New CRM server same SQL, install a new CRM server and point it to the old SQL server
Migration, install a new system with both CRM and SQL, then restore the ORG_MSCRM on the SQL server and import the organization using the deployment administration tool.
You have more info here, and there's also more info in the IG
First, I'm loving the very clearly delineated versioning of the SSIS tools. >:(
I installed SSDT BI for Visual Studio 2013 and built a nice little project in it to generate test data. Within VS 2013, I ran this thing hundreds of times. I can deploy it from within the IDE (right click on project...deploy). However I can't deploy it using the .ispac file.
After much searching, I figured out that VS 2013 is building SSIS 2014 .ispac files (PackageFormat=8) and these won't deploy to a SSIS 2012 server (PackageFormat=6).
My question is, if VS can deploy the package built in VS 2013 to SSIS 2012, is there a way to get this to happen via the .ispac file? I can't deploy to any of my servers (only locally), because I'm not in the same domain (actually, I'm working locally, outside of a domain).
Yeah - the 'versioning' is awesome! NOT.. The simple answer to this is NO, you cannot use a SSIS package built in VS 2013 on Sql Server 2012 - you can deploy is and set it up, etc - but you will get that version 8 to version 6 nonsense..
This link sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi gives you a pretty picture that basically states with VS 2013 you can do SSRS and SSAS on Sql Server 2008, 2012, and 2014 but SSIS only on 2014..
To deploy SSIS packages to SQL Server 2012 you need to build and deploy from VS 2010 or 2012...
Here is the page that explains all the versions - Interoperability and Coexistence (Integration Services) I tried to post the individual links - but I'm new and not allowed...
Hope this helps - this was driving me crazy...
To answer your question directly, no, there is no way to fix the issue in the .ispac file. The dtsx files are different in a couple of ways in SQL Server 2012 and 2014. The only solution I found is to downgrade my packages from VS 2013 to VS 2012.
In case you've already developed significant work in Visual Studio 2013 only to realize that you can't deploy it on SQL Server 2012, I found a workaround how you can "downgrade" your SSIS 2014 packages to SSIS 2012. I wrote it on my blog here:
http://vaniecastro.com/2015/02/26/how-to-downgrade-sql-server-integration-services-2014-packages-to-2012/
The idea is that you need to manually modify the XML file, change the PackageFormatVersion and replace ExecutableType property and componentClassID attribute values to use the DTSX2 Version 2012/01 values instead of the DTSX2 Version 2014/01 ones.