使用 SSISDeploymentManifest 文件，是否可以预先选择安装文件夹？
简短版本：
我有 7 个需要运行的 SSISDeploymentManifest 文件。有没有办法更改 SSISDeploymentManificest 文件以填充安装值？
咆哮版
起初，运行 7 个部署似乎不是什么大问题。但是，为包依赖项“选择安装文件夹”的过程部分设计得非常糟糕。
首先，如果您不是从要安装的服务器运行，则必须在此处输入网络路径。这是因为该对话框确保您在运行清单的本地计算机上输入有效路径...。但是当该包运行时，它也需要适用于服务器。 （愚蠢吧？））
此屏幕的下一个问题是该字段是只读的。所以我不能直接指定路径。
其次，“浏览”对话框不允许我输入路径。
所以...我必须浏览我的整个网络（从家里，通过 VPN）。这需要很长时间。
有没有办法更改 SSISDeploymentManificest 文件以预填充此值？
Short Version:
I have 7 SSISDeploymentManifest files I need to run. Is there a way to alter the SSISDeploymentManifiest file to per-populate Installation value?
Rant Version
At first running 7 deployments did not seem like much of a problem. But the part of the process where you "Select Installation Folder" for package dependencies is horribly designed.
First, you have to enter a network path here if you are not running from the server you will install to. This is because the dialog box makes sure path you enter a valid path... on the local machine you run the manifest from. But when the package is run it will need to also work for the server. (dumb huh?))
The next problem with this screen is that the field is read only. So I cannot just specify the path directly.
Second, the dialog box to "browse" won't let me enter a path.
So... I have to browse my entire network (from home, over a vpn). That takes a long time.
Is there a way to alter the SSISDeploymentManifiest file to pre-populate this value?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不，dtsinstall 不接受任何命令行参数，遗憾。我的第一个方法是编写一个繁重的命令行应用程序，该应用程序重复调用 dtutil 来完成工作。我从未完成过它，但如果你想看一下，它位于 codeplex
我喜欢并更喜欢的是 PowerShell 脚本处理我的 SSIS 部署 现在。即使 PowerShell 不是您的菜，这些概念也应该适用于您可能想要用来处理它的任何 .NET 语言。
它的吸引人的特点是它会为您在 SQL Server 中创建文件夹，并将这些包正确部署到所述文件夹中。可能对您有帮助的另一件好事是，如果所有 7 个部署都在一个公共文件夹结构中，则脚本将遍历文件夹结构寻找清单并部署每个清单的所有包，因此您可以想象用一个单一的部署来部署所有包鼠标点击。
No, dtsinstall doesn't accept any command line arguments, pity. My first approach to this was to write a heavy, command line application that made repeated calls to dtutil to get things done. I never finished it but if you want to peek, it's on codeplex
What I do like and prefer is a PowerShell script that handles my SSIS deployments now. Even if PowerShell isn't your cup of tea, the concepts should apply to whatever .NET language you might want to use to handle it.
Attractive features of it are that it will create the folders in SQL Server for you and correctly deploy those packages into said folders. The other nice thing that might be of assistance to you is that if all the 7 deploys are in a common folder structure, the script walks the folder structure looking for manifests and deploys all the packages per manifest so you could conceivably deploy all with a single mouse click.