将 SSIS 项目/包从 Visual Studio 2017 复制到 2008(部分轻松接受) [英] Copy a SSIS project/package from Visual studio 2017 to 2008 (partial ease accepted)

问题描述

我在 Visual Studio 2017 (SSDT) SSIS 解决方案中创建了几个包，它们显示了目标服务器 2017.这是在我的开发 PC 上.现在，完成它后，我面临挑战.我在其上移动我的包的服务器装有 Visual Studio 2008.

我可以理解降级可能无法立即进行，但如果我能找到一种方法来减少我的工作，我仍然会很高兴(我可以一揽子接受左右).请注意，我正在访问远程上的另一台服务器，无法使用 Ctrl+C 和 Ctrl+V 来复制和粘贴包对象，所以如果我没有得到一些简单的方法，那么几乎必须再次编写整个包.

感谢您的支持.

解决方案

在 Visual Studio 2017 中安装

在 SSIS 项目的 Miscellaneous 部分，您应该有一个 BimlScript.biml 文件.那是 SSIS 包的 Biml 表示，但采用了更简洁但用户友好的语法.此 XML 以独立于版本的方式描述了 SSIS 包的作用.这就是它像黄瓜一样酷的地方:2005 SSIS 包的 Biml 与 2019 包完全相同，反之亦然.Biml 引擎必须知道"如何将包定义转换为特定于版本的 .dtsx，但 Varigence 的聪明人已经解决了这个问题.

现在，您需要使用通用 Biml 并将其与安装了商业智能设计工作室 (BIDS) 位的 Visual Studio 2008/2010 安装相匹配.对于 SQL Server 2005/2008，BIDS 仅出现在 SQL Server 安装介质上，因为这是产品的许可方式.开发者许可证的价格为 25-50 美元，但您无法再购买.希望目标服务器上安装了 BIDS.

如果是这样，那么您需要找到BidsHelper 或者重命名的产品 BI Developer Extensions 然后您可以使用嵌入在该产品中的 Biml 引擎发出 2008 年正确的包.

如果这些都不起作用，您可以尝试为 BimlStudio 和2018 版本仍然允许以 SSIS 2008 为目标.

现在，所有这些都假设您没有使用 2008 年不存在的 SSIS 2012+ 中的任何功能(表达式任务、参数、项目连接管理器等)，我怀疑脚本任务/组件会降级，但好消息是您应该能够将大部分代码复制/粘贴到 2008 版本的对象中.

I have created several packages in Visual Studio 2017 (SSDT) SSIS solution, they are showing target server 2017. This was on my development PC. Now, upon completion of it, I am into a challenge. The Server on which, I am moving my packages, is having Visual Studio 2008.

I can understand that downgrading may not be right away possible, but I will still be happy if I can find a way to minimize my work (i can accept package by package or so). Please note I am accessing the other server on the Remote and not able to use Ctrl+C and Ctrl+V to copy and paste package objects, so if I don't get some easy ways then have to almost write the whole package again.

Thanks for your support.

解决方案

Install BimlExpress in your Visual Studio 2017 environment. Once installed, you should be able to right click on the package and with your new BimlExpress options, select Convert SSIS Packages to Biml

In the Miscellaneous section of you SSIS project, you should have a BimlScript.biml file. That is the Biml representation of an SSIS package but in a much more terse, yet user friendly syntax. This XML describes in a version independent way what the SSIS package did. Here's where it's cool as a cucumber: The Biml for a 2005 SSIS package is exact same as a 2019 package and vice versa. The Biml Engine has to "know" how to translate the package definition into version specific .dtsx but the smart folks at Varigence have already solved that problem.

Now, you need to take that generic Biml and match it up to a Visual Studio 2008/2010 installation that has the Business Intelligence Design Studio (BIDS) bits installed on it. For SQL Server 2005/2008, BIDS only came on the SQL Server installation media as that is how the product is licensed. A developer license cost 25-50 USD but you can no longer purchase it. Hopefully, the target server has BIDS installed on it.

If so, then you need to find a copy of BidsHelper or maybe the renamed product BI Developer Extensions and then you can use the Biml engine embedded in that product to emit a 2008 correct package.

If none of that works, you can try getting a free 7/14 day license for BimlStudio and the 2018 release still allows for the targeting of SSIS 2008.

Now, all of that supposes you haven't used any features in SSIS 2012+ that didn't exist in 2008 (Expression tasks, Parameters, project connection managers, etc) and I doubt a Script Task/Component is going to downgrade but the good news there is you should be able to mostly copy/paste the code into the 2008 version of the object.

这篇关于将 SSIS 项目/包从 Visual Studio 2017 复制到 2008(部分轻松接受)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！