Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Importing SSIS Packages from SQL 2014 to SQL 2016. But they're in RUNNING STATE when executed.

$
0
0

I've imported my SSIS Packages from SQL 2014 to SQL 2016. SQL Server 2014 is in my Local Machine.

1. If I import packages to SQL 2016 which is in my Local Machine when I execute (in SSMS, SSISDB Catalog) the package then status of the package is in Running State and I can still see the operations being executed well (Data is being loaded from source to destination) even it is showing running in my report.

2. If I import packages to SQL 2016 which is in my Remote Machine  when I execute (in SSMS, SSISDB Catalog) the package then status of the package is in Running State and it's not executing.

My Source is a FlatFile in my local Machine and Destination is in SQL Server 2016 (Respectively for Local and Machine(I changed the connections)).

Thank you,

Nihal



Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>