October 15, 2014 at 4:10 pm
I'm working through an upgrade and migration to a new environment. Source is SQL 2005, Destination is SQL 2008 R2. Everything else has gone well, but while upgrading a set of SSIS packages I've hit a new snag that I don't understand. I started a new SQL Server 2008 R2 Integration Services project in BIDS and added each of 7 packages to the solution. I then used the upgrade wizard to convert the packages. The last thing I did was go into each package and replace the connection objects in the Connection Manager to upgrade the OLEDB provider from v1.1 to v10.1. I then saved all the packages without any errors generated and exited the solution. When I came back into the solution, it's as though I didn't do any of that. The packages behaved as though I never saved them. Several iterations later, after checking that my AD/Administrator account had rights to the folders and files, I am still clueless as to why the packages won't save the changes. Any suggestions would be appreciated.
Cheers!
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply