SSIS/SSDT process not responding on new sql server

DSSH 61 Reputation points
2021-03-05T22:12:39.057+00:00

We migrated over from old sql server 2008 to a new one that is 2012. When running a process in SSDT we see “Not Responding” when running a process which is not normal behavior on the old server or when running SSIS or SSDT locally.

When it actually runs it is not showing the typical “hour glass” or donut icon we would see on the container to show that’s it running. It told me the solution/package was running, but nothing actually happened and no data was loaded. It’s a basic import script, nothing is being imported into table from new environment. Any thoughts on how to troubleshoot.
NEW SQL SERVER IS 2012 , OLD SQL SERVER WAS 2008

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,797 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,451 questions
SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,243 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yitzhak Khabinsky 24,941 Reputation points
    2021-03-09T14:17:54.57+00:00

    Hi @DSSH ,

    Are you using Integration Services Catalog and SSISDB database?

    You need to turn on verbose logging, and run the built-in SSIS reports in SSMS.
    It will reveal what is going on.

    75885-ssisdb-catalog.png

    0 comments
  2. Monalv-MSFT 5,891 Reputation points
    2021-03-15T02:04:08.05+00:00

    Hi @DSSH ,

    1.If we execute SSIS Package inside SSDT for Visual Studio, please click Debug > Windows > Output.

    2.If the packages ran from SSMS under SSIS Catalog, please right click on Package > Reports > Standard Reports > All executions.

    3.If the execute the packages not stored in SSIS Catalog in SQL Agent Job, please right click on the job and choose View History.

    Please refer to How to view SSIS Package execution log in Visual Studio / SSIS Catalog Execution / Job Log.

    Best regards,
    Mona

    ----------

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments