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.
Related
I am trying to install Azure biztalk services SDK and then create project in vs 2013 and vs 2015 community edition but dont see any project template.
I can only see project template for biztalk in vs 2012 professional.
This is also made clear in the link here
http://www.microsoft.com/en-au/download/details.aspx?id=39087
However the issue is the microsoft doesnt sell vs 2012 online anymore and i dont see any reason in buying a 3 year old IDE when i have VS 2015.
So just checking if any one here has been able to create biztalk projects for azure in vs 2015.
Its the same problem with Microsoft at Every Release of BizTalk and Visual Studio, the same question you asked get asked everytime
I have VS 2010 but BizTalk project 2006R2 template doesn't appear
I have VS 2012 but BizTalk project 2010 template doesn't appear
...
You have to know that unfortunately BizTalk Project templates are not backward compatible this means that unless you have VS 2012 you won't be able to get those templates.
BUT There is maybe a chance that you can copy those templates from an existing install and get it on your computer (i'll try this at home and edit my answer later) i think it can work if it does i'll post this stuff
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
I have looked through a several forums and cannot find an answer to my specific question so don't hurt me if I have asked something that has been answered before. I have a SSRS report project that was created in Visual Studio 2005 (then upgraded to 2008) before my time at my company and i need to upgrade it to 2013 Visual studio. I know normally you just open the file and use the migration wizard, however i get an error because my Visual Studio 2013 does not recognize the .rptproj file and thus does not fully migrate the solution. I have a copy of VS Shell 2010 that was able to upgrade it to 2010 but this did not help me to migrate it to 2013. Is there a way i can migrate this over without having to buy more copies of VS to do a stair step migration?
You can first check if the Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013 module is installed on your computer.
Were I work we are currently using visual studio 2008 because 2010 did not include the bids stuff, I have now been asked to test out whether 2012 is any better so we have a virtual machine that I've been allowed to work on and we've got visual studio 2012 and 2012 integration services installed on it.
I tried to open one of our solutions which has various report projects in it. When I do this I get a one way upgrade option which I chose and then I get the following:
Projectname.rptproj: The application which this project type is based on was not found. Please try this link for further information: link
This link doesn't work properly and I can't seem to find very much on this for visual studio 2012 am I missing something here? Thanks in advance for any help.
Microsoft has recently released the tools necessary to open and create .rptproj projects in VS2012: Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012
According to this, it appears that you have to install the client tools for VS2012 (from the SQL2012 installer) in order to get the BIDS bits. Incidentally, installing VS2012 client tools will apparently update both VS2010 and VS2012.
While writing this question I had a simple idea which fixed the issue. Maybe other people have the same problem or you would like to comment this so I'm posting it anyways.
tldr/simplified question:
How do i use MS SQL Server 2005 Reporting Services in Visual Studio 2010?
Solution:
Just copy the Visual Studio 2008 Reporting DLLs in your project and include them as references. I guess you have to own a licence for vss2008 when doing this but technically this solves the issue.
Original question:
How can i use MS SQL Server 2005 Reporting Services in Visual Studio
2010? The reason i ask this is the following: We migrated to
VSS 2010 as our IDE but are still using MS SQL Server 2005.
Now, i want to change a piece of code in a Project which makes use of
Reporting Services on said SQL Server.
After converting the Solution to a VSS2010 Solution I get BuildErrors
because it can't find the namespaces "ReportViewer" and "Reporting".
That's because the references to
Microsoft.ReportViewer.Common (9.0.0.0)
Micrsofot.ReportViewer.WinForms (9.0.0.0)
Are no longer resolvable. So i have to replace them with the
references to the same Assemblies in Version 10.0.0.0.
After doing that the Solution builds successfully, but when opening
the ReportViewer i get an SoapVersionMismatchException telling me that
for Remote-Processing i have to use Microsoft SQL Server 2008
Reporting Services or higher.
You need to add the old references to your project. You can find them on your 2005 reporting server.
These can be found on your reporting server in the GAC.