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
Related
I have a client who has Visual Studio Tools for Applications 2015, 2017 and 2019 installed. They are in the process of moving to a new server and need to identify what version the SSIS packages (that are deployed to the SQL Server) are using. How do I get that information?
Thanks.
We have assumed maintenance of a legacy 32bit application. I installed TFS 2008 to use in maintaining the project.
We will never use reporting or sharepoint. I cant create a project because of issues with SSRS.
(The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on OHSENSS801. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the SQL Server Reporting Services site. )
How can I disable reporting and sharepoint in TFS 2008?
Thank you.
Unlike TFS 2010 and above version, you have to install the SharePoint components for TF2008.
TFS2008 is a very old server version and out of support for a long time. You could use TFS2010 instead, the SharePoint is no longer a prerequisite when you install TFS2010. You can go for TFS2010 Basic Configuration which is the most compact TFS installation possible.
In Basic Configuration, SharePoint and Reporting Integration will not be possible. It will install and configure Source Control, Work Item tracking and Build Services only.
Highly recommend you to move to a newly versioned TFS server. If you insist on using TFS2008, you could try to troubleshoot the configuration of SQL Server Reporting Services. Details please refer this thread in MSDN: SQL Server Reporting Services is not configured correctly
About how to remove Sharepoint and Reporting Services from TFS, you could go through this question. However, afraid removing these components, you will still not able to create team project. After all, if it will work, there is no need to be a prerequisite for installing TFS2008.
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
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)
I installed MySQL connector for .Net v6.5 and it is supported by Entity Framework. When I use Visual Studio 2012 and try to add an ADO.NET Entity Data Model, I can't see MySQL. There are just Microsoft SQL Servers. It worked in VS 2010.
This question said that they are working on it - is there a conclusion?
use this mysql connector for vs 2012. once you install it then you have no such error and
mysql server shows in datasource.
http://dev.mysql.com/downloads/connector/net/6.6.html
The connector .NET v6.5.4 available today does not support VS 2012. You can't add a connection to MySQL in the Server Explorer to begin with.
Support will be included in 6.5.5 as per post: MySQL forum
There is apparently some workarounds and 3rd party ways to get this working but personally I will just wait.
Just to provide an update: The 6.5 version of the connector does NOT support VS2012.
But there is a development release of 6.6 that does.
Go to the following URL and click on the tab "Development Releases" to download it:
http://dev.mysql.com/downloads/connector/net/#downloads
Download "MySQL.Connector.Net.6.5.4.VS2012.vsix" and install it to be able to use MySQL in Visual Studio 2012.
You might need to restart Visual Studio after installing it to see the changes.