Recently because of an ETL compatibility problem, I foolishly installed SSDT2012 Chinese version and SSDT English version of Half
Then my SQL client had a problem, half of it couldn't be uninstalled, it was completely uninstalled and it was too cumbersome, and then
And only part of the function can not be used, so find another path.
The error is as follows
1. When the client deploys the ETL package and imports the package:
Deployment Package
Title: SQL Server Integration Services
------------------------------
Failed to load type from assembly "Microsoft.SqlServer.Dts.Design, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91" Microsoft.SqlServer.Dts.Design.VisualStudio2012Utils ". (Microsoft.SqlServer.IntegrationServices.Wizard.Common)
------------------------------
Button:
Are you sure
------------------------------
Importing packages
2. When the database task imports and exports data
Treatment methods
Use a different server SQL client to connect to my native server to complete these operations
First locate the native IP address in the local:cmd>ipconfig>
Then ping your local computer on the server to see if it can be ping, such as Ping
If the ping does not work, then shut down the firewall, my side is to shut down the domain network firewall,
Then: All Programs >microsoft SQL Server 2012> Configuration tool >sql Server Configuration Manager
SQL Server Network Configuration
In TCP/IP, you can right-click Properties, as below, to modify IP
Then, check the local server properties to allow remote connections to this server to hook up.
Finally try to connect to the other server, give the login account sufficient permissions, you can connect the native database service on the other server for ETL deployment, database task import and export, etc.
Connection Successful!
Ending ~ ~
How can other servers connect to their own native databases?