Is there a way of converting a SSIS package created in Visual Studio 2013 to work on SSIS 2012?
The start of my package looks like this:
<?xml version="1.0"?>
<DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts"
DTS:refId="Package"
DTS:CreationDate="12/18/2014 8:53:33 AM"
DTS:CreationName="Microsoft.Package"
DTS:CreatorComputerName="LOCAL111"
DTS:CreatorName="username1"
DTS:DTSID="{C6D60123-5529-4BC1-B426-B219A0709EB7}"
DTS:ExecutableType="Microsoft.Package"
DTS:LastModifiedProductVersion="12.0.2430.0"
DTS:LocaleID="1044"
DTS:ObjectName="ZVENDGLO import"
DTS:PackageType="5"
DTS:VersionBuild="321"
DTS:VersionGUID="{E6195A4D-907C-4597-8448-C4E56027883A}">
<DTS:Property
DTS:Name="PackageFormatVersion">8</DTS:Property>
<DTS:ConnectionManagers>
...
Thanks,
Thomas
The short and long answer, unfortunately, is no. If you want to develop SSIS/SSDT for SQL Server 2012, you must use the Visual Studio environment that came with 2012.
Here's the long version of the background info. To build SSDT packages for SQL Server 2012, you actually use Visual Studio 2010. VS2010 is the BIDS environment that came with SQL Server 2012. People very colloquially call it SSIS 2012, but that's a misnomer, and with the very weird backwards compatibility issues surrounding SSIS across these versions, it's important to get the terminology about development environments right. Additionally, you are developing packages in Visual Studio 2013, but that technically is only for SQL Server 2014.
The interesting thing is you can use VS2013 (the developer tools included with 2014) to build SSRS and SSAS solutions for SQL Server 2008 through present, but that flexibility does not extend to SSIS/SSDT. You must use SSDT for VS2010 if you want to deploy packages on SQL Server 2012, and you must use SSDT for VS2013 if you want to deploy packages for SQL Server 2014.
Sources:
http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
Anyway to deploy a SSIS 2012 project built in VS 2013?
https://msdn.microsoft.com/en-us/library/bb522577.aspx
Related
Is it possible to open a SSIS solution using Microsoft's free tools (Visual Studio Team Explorer and SQL Server Data Tools) or does it require a full installation of Visual Studio?
I am trying to do so with just the free tools and am getting an error saying that "this versino of Visual Studio is unable to open the following projects" then another one saying the solution I have opened is under source control but not currently configured for integrated source control in visual studio.
We have other users who use the full version of Visual Studio 2017 and it works fine so I am wondering if this is just a limitation of the free products offered by Microsoft.
To edit SQL Server 2005 SSIS packages, you need Visual Studio 2005 and installation of Business Intelligence Designer Studio, BIDS. This required a license, developer edition was sufficient, to access the tooling.
SQL Server 2008 & SQL Server 2008 R2 would install into Visual Studio 2008. This too required a SQL Server license as the media only existed on the server media.
SQL Server 2012 would install into both Visual Studio 2010 and Visual Studio 2012. This was delivered in both physical media installations and downloadable tooling which was rebranded to SQL Server Data Tools- BI Edition, now just SQL Server Data Tools and the components were just licensed via click through agreement.
SQL Server 2014 installs into Visual Studio 2013 and was now only available through the download of SSDT.
SQL Server 2016 added a new twist into the mix. It installed into Visual Studio 2015 but it could now create/edit/target SQL Server 2012, 2014 and 2016 packages. This was huge as until this point, as a consultant I would have required 5 different versions of the "same" program on my machine. Now I'd only need 3.
SQL Server 2017 installs SSDT in both Visual Studio 2015 and Visual Studio 2017.
I assume SQL Server 2019 will similarly target VS 2017 and VS 109.
Across all of these versions, if you didn't have Visual Studio installed, the installer would install the Visual Studio shell on your machine so that the project templates would work.
Last I knew, neither Visual Studio Community Edition nor VS Code will work with the SSDT templates so be sure and open the correct product to work with SSIS projects (.dtproj)
The warning/error about "under source control but not currently configured" smells like something is awry with how you have the TFS hook installed but I can't comment on that.
Download and install SSDT 2017 for Visual Studio
You can verify the status of your SSDT installation for Visual Studio by going to the Help, About Microsoft Visual Studio menu and looking for "SQL Server Integration Services." With ... 2017? you can now do a piecemeal install and only pick SQL Server Data Tools (database projects) or SSAS/SSIS/SSRS. Previously, the SSDT-BI install was trio of SS_S and SSDT (no BI) was the database projects.
Previous answer on where SSDT-BI is
You have at lease two options:
Use Visual Studio Community Edition together with SSDT. Still, you have to check its License terms with your Legal department - it might be not legal to use Community Edition in Enterprise.
Use Visual Studio Isolated Shell together with SSDT. More instructions on how to install it. As far as I know, it is legal to use it for debugging.
The VS Isolated Shell is usually installed with SQL Server 2014/16.
We have Visual Studio 2010 with .Net Framework 4.5
and SQL Server version 2008.
We are in the process of migrating SQL Serer 2008 to 2014.
I want to know the steps to migrate to 2014 and is there any settings or extensions or updates to be done for Visual Studio to make it compatible with SQL Server 2014?
For full support of SQL Server 2014 inside Visual Studio, you need to run at least Visual Studio 2012 and have SSDT installed as outlined here.
However, to connect to SQL Server from your application or from Visual Studio and to do basic operations against the database no update to Visual Studio 2010 is required.
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.
I was using reportviewer 2010 control in visual studio 2010 but i need to start using reportviewer 2012. How can I use the new ASP.NET webforms ReportViewer 2012 control in Visual Studio 2010 (without moving up to visual studio 2012)? Eventually I want to move up to Visual Studio 2012 and dotnet 4.5 but I'd prefer to keep using dotnet 4.0 and Visual Studio 2010 for a little while longer.
I think you are asking how you can 'create reports' for SSRS by the sounds of it, not just display them. Okay so this will sound weird but you need SQL Server 2012 either Enterprise, Developer, Standard with Advanced Tools edition. Any one of those should suffice to get you the tool you need. If you are looking to 'design' reports the tool is an add on to Visual Studio called 'Business Intelligence Development Studio', BIDS for short. For some reason it shows up now as 'SQL Server Data Tools' under 'All Programs' on Windows. You can thank Microsoft for making this version as confusing as possible to people looking to get into SSRS.
To install it you simply install all of SQL Server and when you get to the 'Features' section ensure that BIDS is selected. The version of BIDS IS NOT ON VS 2012, it is on VS 2010. For some reason the SQL team did not make the deployment of SQL Server coincide with Visual Studio so it goes along with VS 2010, NOT 2012. A great many people get this confused but I can say for a fact SSRS is an extension of BIDS, which in turn is an extension of Visual Studio. Not the other way around. You can create localized reports in VS 2012 that are 'rdlc' files but not the full blown SSRS you deploy to a server there.
I know that VS 2010 can target specific .NET Framework editions, but specifically...
Can I use VS2010 to support SSIS packages that need to be saved in 2005 format?
How about VS2008?
I am trying to determine which edition I need get a license for. I am hoping I can do everything in 2010.
I do not believe that Visual Studio 2010 is supported by SSIS yet (even with SQL 2008 R2 I use VS 2008). However, if you have SSIS it should come with Visual Studio 2008. It is called the Business Intelligence Development Studio (BIDS) and it installs with SSIS.
As for targeting an older SSIS project, I believe 2008 will target 2005. You just need to install the SSIS management studio and you will have it.
Edit: To be clear, BIDS 2008 will not be able to modify 2005 packages (I believe you can run them though). You will need to install just BIDS (not the entire Visual Studio) for each version you want to modify. Here is a link with more explanations:
http://social.msdn.microsoft.com/Forums/en-ZA/sqlintegrationservices/thread/4fe1b042-3f8d-473d-b9fe-2c4adeb67bcd
As for licensing specifically, you will need a developer license for SSIS at the version level you are trying to edit. Therefore, if you are editing SSIS 2005 packages, you will need a 2005 SSIS developer license. See more details here:
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/0b2754aa-716e-4f81-85c0-3b6dcdc34bb3/