April 21, 2006 at 11:47 am
Hello!
I'm using the SSIS Package Migration Wizard to migrate SQL Server 2000 DTS packages. I followed all of the steps documented in Microsoft's 'SQL Server 2005 Books Online Using the Package Migration Wizard'. After I completed the migration, it says "you should connect to the local instance of Integration Services in Object Explorere to see the migrated packages. If you selected SQL Server as the destination, the migrated packages will be visible under the MSDB node'." When I checked, nothing showed up in this area. The logs showed that the migration completed successfully, and the dbo.sysdtspackages90 showed all 22 packages that I migrated. Additionally, if I tried to use the wizard a second time, it tells me that the files have already been migrated.
Has anyone else experienced this problem? If so, how did you rectify the problem? If you successfully migrated the SQL Server 2000 DTS to 2005 with the migration tool, could you tell me how you did it and where you were able to find the migrated packages in SQL Server 2005?
Thanks!
Amy
April 21, 2006 at 12:51 pm
When running a default instance of SQL 2000 and a named instance of SQL 2005, I ran into a problem with the configuration of SSIS where it uses the default instance of SQL Server instead of the named instance. Look in this file:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
If the database server here is not your 2005 server, this could be part of your problem.
-Pete
April 21, 2006 at 1:01 pm
Hi Pete,
It looks like we don't have the subdirectories under C:\Program Files\Microsoft SQL Server\90\ that you mentioned. I'll have to find out why we don't have DTS\Binn.
Thanks!
Amy
April 21, 2006 at 1:16 pm
Might be in a different location - depends on where things were installed. Perhaps do a search for that file across all of your drives? It might not even relate to your issue, but is worth checking out.
-Pete
April 21, 2006 at 1:23 pm
I did search the entire drive, and couldn't find the file that you were mentioning. Maybe we missed the installation of something. Would you have any clue what could be missing? Thus far, I'm really not sure and I haven't found any answers on the web either.
Thanks again,
Amy
April 21, 2006 at 2:14 pm
Hi Pete,
I found out that although there was a similar path on our c-drive, it was actually installed on a different drive. Once we modified the xml file that you mentioned, it worked.
Thanks so much for your help!!!
Regards,
Amy
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply