When creating a new Integration Services Project in Visual Studio 2013 I can select the .NET framework to target. How can I see what .NET framework is being targeted on an existing project and potentially change it?
You need to open one of the Script Tasks and click the "Edit script..." button. This will open the script on a new instance of Visual Studio with the script in its own project. There you can change the properties of that project to modify the targeted framework for that particular Script Task.
There is no .NET Framework targeting for SSIS packages. However, there IS SQL Server version targeting. Prior to Visual Studio (VS) 2015, it was a bit of a mess: you could only target a specific version of SQL Server with a specific version of Visual Studio. For example:
SQL 2008 = VS 2008
SQL 2012 = VS 2012
SQL 2014 = VS 2013
With the release of VS 2015, however, Microsoft alleviated some of the headache by introducing SQL Server targeting within VS by just right clicking on the solution, going to properties, and selecting the version of SQL Server that the SSIS package would run on. This is important because it determines what components are available to use.
Now, with that being said, there is .NET Framework targeting within script tasks/components. To read more about that, check my answer at:
SSIS Script Keeps Reverting To .Net Framework 4.5
Related
I observe that CreateDeploymentUtility is not available in same place as it should be as explained in this video. By any chance do you know where I can find and set it?
I am using Microsoft Visual Studio Enterprise 2017, version 15.3.4, .Net Framework version 4.7.02046
The SQL Server 2017 Integration Services (SSIS) introduced the
Incremental Package Deployment feature that allows you to deploy one
or more packages without deploying the whole project.
To Deploye follow steps given in below Link.
https://learn.microsoft.com/en-us/sql/integration-services/packages/deploy-integration-services-ssis-projects-and-packages#PackageModel
I'm new to SSRS.
Recently upgraded my development environment from Visual Studio 2010 to Visual Studio 2015 Enterprise Edition. Currently my reports are made using Crystal Reports. I would like to to use SSRS and I'm trying find out my current environment will allow me to do it.
So now I'm using Visual Studio 2015 and SQL Server 2008 R2.
Can I create SSRS Reports using these two?
If yes, how can I create it?
I know how to create a report and publish it using the Business Intelligence Development Studio in SQL Server 2008 R2. But could not understand how I could use those reports in my WebApplication project in Visual Studio 2015.
Also would like to know - Is it possible to reuse my existing datasets which I'm using in my Crystal Reports?
Should I upgrade my SQL Server version?
Yes, you can create reports for SSRS 2008 R2 with VS 2015. You will need to download, and install, the SQL Server Data Tools (SSDT) at the following link.
https://msdn.microsoft.com/en-us/library/mt204009.aspx
To build reports, create a new project using the Report Server Project template found under Templates/Business Intelligence in the New Project dialog. (After you install SSDT)
This is the replacement for BIDS, so much of what you see should look familiar.
Not sure about the Crystal Reports datasets, but you should be able to reuse any SQL or stored procedures that may be a part of these.
Should you upgrade? At some point, sure, but it isn't required. SQL Server 2016 is about to be here, and you are working with a product that is over 4 years old, and more than likely going to be out of support soon, if it isn’t already.
There is a setting in Visual Studio (See above answers for more details.)
There is a setting in
Project --> Properties --> TargetServerVersion
Note that here, server means database server or db-server, as opposed to web server or report-server.
But note well: For me, it is only the version in the folder:
..Projects\myProject1\myProject1\bin\Debug
that will actually deploy and work.
I am trying to deploy a Script component to SSIS toolbox in the Data Flow for reuse. I'm using visual studio 2010, and SQL server 2014.
I have created the script, Signed the assembly, used Gacutil.exe /i on the DLL file to add it. It now recedes in the GAC_MSIL folder under it's strong name folder.
The above procedure is the current way I'm trying to get it to work, but I have additionally tried to use SN utility to generate a strong name and add this key back into the build. Didn't work any better than the above procedure. Is it supposed to be next to impossible to add custom components to SSIS?
In my simple mind it should be just sign, build, GAC and done.
The editor for SSIS packages is tightly bound to the version of the SQL Server you're working with.
As a general reference, we have the following
VS 2005 = SQL Server 2005 {90}
VS 2008 = SQL Server 2008 & SQL Server 2008 R2 {100}
VS 2010, VS 2012 = SQL Server 2012 {110}
VS 2013 = SQL Server 2014 {120}
VS 2015 = SQL Server 2016 (once it's RTMed) {130}
Now, you could be using VS 2010 to build your custom DLL, as long as you've referenced the correct version of the SSIS DLLs, and then used SSDT-BI edition for VS 2013 to author your SSIS packages --- that's fine.
Making it work
Your current build and deploy cycle is what you need to do on your servers. That will allow SSIS to find the components when it runs.
However, you need the development experience so you need to also add that same DLL into the correct folder in your SQL Server installation. For SQL Server 2014, a custom "Script Component", or anything that lives in the data flow, would also need to be copied to
C:\Program Files\Microsoft SQL Server\120\DTS\PipelineComponents
If you've done it properly, then items automatically show up for VS 2010+. VS 2005/2008 required an additional step of explicitly adding tasks and components into the Toolbox.
If they aren't showing then you've either
built your DLL against the wrong version of the SSIS framework
using the wrong version of SSIS tools
not deployed the DLL to both the GAC and the correct DTS subfolder based upon your SQL Server version.
Clear as mud?
My development environment: SQL Server 2014, Visual Studio 2015, SQL Server Data Tools Preview (September) for Visual Studio 2015
I have a custom SSIS source component that I can successfully use on another SQL 2014 box with VS 2013 and SQL Server Data Tools - Business Intelligence. However, this component does not show up in the toolbox in VS 2015 Integration Services project.
The component is located in c:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents. It is also registered in GAC.
Do I need to make changes to the component so that it will work with VS2015?
More general question: how to troubleshoot issues like this?
I've managed to get the problem of adding a custom SSIS component to a Visual Studio 2015 SSIS package. This maybe have been enabled by the release of SQL Server 2016 CTP 3.2, but I thought that I'd put this out there in case it helps anyone.
First of all let me just let everyone know what system I'm using in case this doesn't work for everyone:
My system is: Windows 8.1 64 bit
Visual Studio Community 2015 Version 14.0.24720.00 Update 1
Microsoft SQL Server Integration Services Designer Version 13.0.900.80 (I've installed the SQL Server 2016 CTP3.2 so the version of SSIS is this version - this may be part of the problem and it isn't a fully released product and this may be a bug)
Microsoft .NET Framework Version 4.6.01055
In my c# class project I used the .NET Framework 4.6
(Project Properties->Application).
I made sure that I added to the gac using the gacutil.exe in the following folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools
and I copied the dll to the following folder:
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents
After refreshing the SSIS toolbox the component now appears in the Common folder/subsection.
I hope this works for everyone or is at least of use to anyone else who has had this problem. I was so happy after trying nearly everything and it coming up blank to see the component appear in the SSIS toolbox and know how frustrating this kind of thing can be!!!
Matt
In VS2015 Solution Explorer, right click on the .dtproj file and select properties. On the General Tab choose the SQL Server version that matches the component version. If the component worked on VS2013, choose 'SQL SERVER 14' when opening the package in VS2015.
I have not seen the SQL Server 2014,just wondering is there any difference in SSIS 2012 and SSIS 2012?Any new components introduced?Any new tasks?
According to the MSDN article What's New (Integration Services), no changes have been introduced in SSIS:
SQL Server 2014 Integration Services is unchanged from the previous release.
Feature wise they are exactly the same but for some stupid reason the package format has changed and you cannot mix versions.
i.e. Packages created in VS2010/2012 can only be deployed to SQL 2012 instance (SSIS2012 runtime) and VS2013 -> SQL 2014.
If you open a VS2010/2012 solution in VS2013 it will upgrade and you cannot go back.
See this for more feedback.
http://connect.microsoft.com/SQLServer/feedbackdetail/view/944882/ssdt-bi-2014-backward-compatibility-for-ssis-2012
Edit: it seems you can deploy SSIS2012 packages to SQL2014 using Management Studio as they are automatically upgraded. The rules about Visual Studio still stand.
(I have used this - my team are mixed between 2012 and 2014)