SSIS：从VS部署后，connectionstring中断

I have a server with 64-bit MS SQL Server 2016 installed.

我有一台安装了64位MS SQL Server 2016的服务器。

I have a SSIS package which contains ACE OLEDB 12 connection manager, which builds a connection string using package variable FileName (String).

我有一个SSIS包，其中包含ACE OLEDB 12连接管理器，它使用包变量FileName（String）构建连接字符串。

So, if I deploy this package to SSISDB from Visual Studio 2015 (DataTools) just from the server itself, all is ok.

因此，如果我从Visual Studio 2015（DataTools）仅从服务器本身将此包部署到SSISDB，一切正常。

But, when I deploy the same package using Visual Studio 2015 (DataTools) from my local PC, it corrupts the connection string: all non-ASCII symbols became broken! So, the package fails validation and not starts on the server after deploy. So the problem comes when I use my local VS to deploy the package / project; if I go to SSMS on my local PC, connect to server, go to the SSISDB, and deploy a project from here, the connection string deploys properly.

但是，当我从本地PC使用Visual Studio 2015（DataTools）部署相同的软件包时，它会破坏连接字符串：所有非ASCII符号都被破坏了！因此，程序包验证失败，而不是在部署后在服务器上启动。所以当我使用我的本地VS来部署包/项目时就会出现问题;如果我在本地PC*问SSMS，连接到服务器，转到SSISDB，并从此处部署项目，连接字符串正确部署。

What setting (maybe, collation, or connection string codepage) can be changed to let me deploy a package / project from VS? I've searched in project and solution properties with no success. Thanks

可以更改哪些设置（可能是排序规则或连接字符串代码页）以让我从VS部署包/项目？我在项目和解决方案属性中搜索没有成功。谢谢

1 个解决方案

#1

Problem solved: use ACE OLEDB 15 provider instead of 12.

问题解决：使用ACE OLEDB 15提供程序而不是12。