We are in a process of migrating our SQL Server 2005 to the 2012 version.
我们正在将SQL Server 2005迁移到2012版本。
There's a significant number of SSIS (developedn in VS 2005) running on this server.
在这台服务器上运行了大量的SSIS(在VS 2005中开发)。
Will it be ok to just re-deploy these packages on the new SQL instance?
是否可以在新的SQL实例上重新部署这些包?
Or will I have to go through the Visual Studio upgrade process for each?
或者我是否必须为每个进行Visual Studio升级过程?
Any comments, advice appreciated.
任何评论,建议表示赞赏。
Thanks in advance.
提前致谢。
1 个解决方案
#1
3
You're looking at the upgrade, for a variety of reasons.
由于各种原因,您正在考虑升级。
In 2005, packages would have been stored in msdb.dbo.sysdtspackages90 From 2008 forward, that table was renamed to msdb.dbo.sysssispackages
在2005年,软件包将存储在msdb.dbo.sysdtspackages90中。从2008年开始,该表被重命名为msdb.dbo.sysssispackages
Even if you deploy them into sysssispackages and kept a 2005 Integration Services Service installed, I don't think the 2005 dtexec would work with the 2008 version of the stored procs in msdb relative to SSIS work. The procs should be backwards compatible for the msdb SSIS "stuff" in 2012 as they poured all of their attention into the 2012 SSISDB catalog and the CLR methods there.
即使您将它们部署到sysssispackages并保持安装了2005 Integration Services Service,我也不认为2005 dtexec可以使用msdb相对于SSIS工作的2008版本的存储过程。这些过程应该在2012年向后兼容msdb SSIS“东西”,因为他们将所有注意力都集中在2012年的SSISDB目录和那里的CLR方法上。
Depending on your Connection Managers, the SQL Server OLE DB connection strings changed from SQLNCLI01 to SQLNCLI1.0 (approximate)
根据您的连接管理器,SQL Server OLE DB连接字符串从SQLNCLI01更改为SQLNCLI1.0(近似值)
The internals of how Data Flows works has also changed. The mechanism for signaling the end of rows changed between 2005 and 2008 so if you have any custom components, those will have to be reworked.
数据流如何工作的内部也发生了变化。用于发送行结束信号的机制在2005年到2008年之间发生了变化,因此如果您有任何自定义组件,则必须对其进行重新设计。
When you convert from 2005 to 2012, you can migrate to a Project Deployment model or the Package Deployment Model. As it seems you are looking for a minimum of change, stick with Package Deployment Model. The project deployment model will entail forgoing your Configurations in lieu of the fancy new Parameter methodology.
从2005转换为2012时,可以迁移到项目部署模型或包部署模型。由于您似乎正在寻找最小的变化,因此请坚持使用Package Deployment Model。项目部署模型将需要放弃您的配置,而不是花哨的新参数方法。
#1
3
You're looking at the upgrade, for a variety of reasons.
由于各种原因,您正在考虑升级。
In 2005, packages would have been stored in msdb.dbo.sysdtspackages90 From 2008 forward, that table was renamed to msdb.dbo.sysssispackages
在2005年,软件包将存储在msdb.dbo.sysdtspackages90中。从2008年开始,该表被重命名为msdb.dbo.sysssispackages
Even if you deploy them into sysssispackages and kept a 2005 Integration Services Service installed, I don't think the 2005 dtexec would work with the 2008 version of the stored procs in msdb relative to SSIS work. The procs should be backwards compatible for the msdb SSIS "stuff" in 2012 as they poured all of their attention into the 2012 SSISDB catalog and the CLR methods there.
即使您将它们部署到sysssispackages并保持安装了2005 Integration Services Service,我也不认为2005 dtexec可以使用msdb相对于SSIS工作的2008版本的存储过程。这些过程应该在2012年向后兼容msdb SSIS“东西”,因为他们将所有注意力都集中在2012年的SSISDB目录和那里的CLR方法上。
Depending on your Connection Managers, the SQL Server OLE DB connection strings changed from SQLNCLI01 to SQLNCLI1.0 (approximate)
根据您的连接管理器,SQL Server OLE DB连接字符串从SQLNCLI01更改为SQLNCLI1.0(近似值)
The internals of how Data Flows works has also changed. The mechanism for signaling the end of rows changed between 2005 and 2008 so if you have any custom components, those will have to be reworked.
数据流如何工作的内部也发生了变化。用于发送行结束信号的机制在2005年到2008年之间发生了变化,因此如果您有任何自定义组件,则必须对其进行重新设计。
When you convert from 2005 to 2012, you can migrate to a Project Deployment model or the Package Deployment Model. As it seems you are looking for a minimum of change, stick with Package Deployment Model. The project deployment model will entail forgoing your Configurations in lieu of the fancy new Parameter methodology.
从2005转换为2012时,可以迁移到项目部署模型或包部署模型。由于您似乎正在寻找最小的变化,因此请坚持使用Package Deployment Model。项目部署模型将需要放弃您的配置,而不是花哨的新参数方法。