将 SSIS 包从 SQL Server 2005 迁移到 2008 时要记住什么？
将 SQL Server Integration Services 包从 SQL Server 2005 数据库移动/导出到 2008 的最佳实践是什么？
有哪些安全问题？
What are best practices for moving/exporting SQL Server Integration Services Packages from a SQL Server 2005 DB over to 2008?
What are some of the security concerns?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明，从 2005 年迁移到 2008 年并不像看上去那么糟糕。 我读到的所有内容都表明 Visual Studio 2008 环境会自动将 SSIS 包转换为更新的格式。
需要注意的重要一点是 Visual Studio 2008 将能够运行 SSIS 2005 包。 但是，当您在设计器中保存包或使用转换工具时，包将被转换为 SSIS 2008 格式，并且将无法再次在 Visual Studio 2005 中使用。
我对升级过程做了一些重要的说明：
VSA（Visual Studio for Applications）
SSIS 2005 中已替换为
VSTA（Visual Studio 工具
SSIS 2008 中的应用程序。
升级过程通常运行良好。
但是，如果您使用任何参考
IDTSxxx90接口，需要
确保它们已更新为
参考 IDTSxxx100 接口。
提供商名称略有变化
SSIS 2005 和 SSIS 2008 之间
SQL 本机客户端和 OLE DB
连接字符串，因此请确保
使用升级向导或手动
检查连接字符串设置。
我发现的有关所有这些信息的一些资源来自：
SSIS 2008 Cribsheet
MSDN 集成服务倒退
兼容性文档
Michael Entin 的笔记本 (MSDN
博客）
...嘿，我也学到了一些东西，因为我们正准备解决同样的问题。
It turns out that migrating from 2005 to 2008 isn't as ugly as it may seem. Everything I've read indicates that the Visual Studio 2008 environment will automatically convert the SSIS package to the newer format.
An important thing to note is that Visual Studio 2008 will be able to run SSIS 2005 packages. However, the moment you save the package in the designer or use the conversion tool, the package will be converted to SSIS 2008 format and will not be able to be used in Visual Studio 2005 again.
A few important notes I've made about the upgrade process:
VSA (Visual Studio for Applications)
in SSIS 2005 has been replaced with
VSTA (Visual Studio Tools for
Applications in SSIS 2008. While the
upgrade process typically works fine.
However, if you use any references to
IDTSxxx90 interfaces, you need to
make sure they were updated to
reference IDTSxxx100 interfaces.
Provider names have changed slightly
between SSIS 2005 and SSIS 2008 for
SQL Native Client and OLE DB
Connection Strings, so make sure to
use the upgrade wizard or to manually
check the connection string settings.
A few resources I've found regarding all this information comes from:
SSIS 2008 Cribsheet
MSDN Integration Services Backwards
Compatability documentation
Michael Entin's Notebook (MSDN
Blog)
...hey, I learned something too since we're getting ready to approach this same issue.