I have a series of packages that use Cached Connection Managers for lookups. The packages were working just fine while the DB was 2008R2. Still using Visual Studio 2008, I can run the package in BIDS and the Data Flow Task that populates the Cached CM runs OK. When I deploy the package to a SQL 2012 SSIS box (from VS 2008, so basically same model as before) the package hangs. If I disable the DFT to populate the CM, and re-deploy, it goes through just fine.
Is there an issue with SQL 2012 populating Cached Connection managers? I would hate to have to re-design because that on Cached CM (containing 1/2 million rows) is consumed about 10 to 15 times per day.
Thanks in advance.
Todd C - MSCTS SQL Server 2005, MCITP BI Dev 2008 Please mark posts as answered where appropriate.