June 9, 2009 at 3:39 pm
Hi,
We are upgrading SQL Server 2000 standalone to Clustered SQL Server 2005(Active/Passive). I migrated the databases using backup restore and moved the jobs, logins everything went well so far.
Now we have DTS package in SQL server 2000. It is very complex DTS package to migrate to SSIS. So we decided to use the same DTS package. I moved the DTS as below:
1. Open the DTS package in SQL Server 2000 and select package->save as->here selected the new sql server name virtualserver\ins1 and the pakage saved in new server
2. To edit DTS package in SQL Server 2005, I installed sqlserver2005_dts.msi.
my question is Do I need to install this sqlserver2005_dts.msi on node 2(Passive) also?
Is the above method used to move DTS package to sql server 2005 is correct?
and we have a sql agent job for that package in sql 2000as below
dtsrun /S ABC /E /N Import /A gstrServer:8=ABC /A gstrClient:8=CF /A gstrEnvironment:8=Prod /A gstrPath:8="C:\"
sql 2000 is default instance ABC. Now in the above job step, if change the ABC to virtualserver\ins1, then the job should work right?
please advice
thanks
June 11, 2009 at 1:05 am
could you please give me some info.....
June 11, 2009 at 8:38 am
Hey, I've said it before on here. DTSxChange from pragmaticworks.com is the thing to use. If you only have one package, just download the free three package trial 😀
June 12, 2009 at 4:57 am
Personally, I would install the DTS designer component on all nodes. That way you can use it regardless of which node is active.
Also, I recommend you use the freeware DTSBackup2000 to export and import your packages. The Save As... method in SQL 2000 EM looses all the layout and annotations from your package, but DTSBackup2000 keeps all this.
Many installations find they need to apply the KB917406 fix to get DTS Designer to open all their packages.
You can run DTS packages in 64-bit as well as 32-bit servers. On 64-bit, you need to put any DTS components (e.g. OCX) into the Windows \SysWOW64 folder instead of the \System32 folder, otherwise they will not be found.
When it is convenient to you to convert to SSIS, then DTSxChange is one of the best ways to do this.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply