ssis-2016

来源： https://stackoverflow.com/questions/63395245/unexpected-termination-when-loading-data-from-excel-using-ssis

来源： https://stackoverflow.com/questions/63395245/unexpected-termination-when-loading-data-from-excel-using-ssis

问题 i was querying the ssis catlog to find out the name of all the packages in the catalog. There are only 6 packages in the Folder1 project,but the query gives 9 records 1. SELECT P.NAME FROM SSISDB.internal.projects PRJ INNER JOIN SSISDB.internal.packages P ON P.project_version_lsn=PRJ.object_version_lsn WHERE PRJ.NAME='Folder1' Does it show the deleted packages from the project as well. 回答1: They aren't deleted, that's part of the historical tracking. You likely wanted a query more similar to

问题 i was querying the ssis catlog to find out the name of all the packages in the catalog. There are only 6 packages in the Folder1 project,but the query gives 9 records 1. SELECT P.NAME FROM SSISDB.internal.projects PRJ INNER JOIN SSISDB.internal.packages P ON P.project_version_lsn=PRJ.object_version_lsn WHERE PRJ.NAME='Folder1' Does it show the deleted packages from the project as well. 回答1: They aren't deleted, that's part of the historical tracking. You likely wanted a query more similar to

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the

问题 We have many SSIS imports in our environment all created with SQL / Visual Studio 2008 version. We run a lot of imports from SharePoint and for that we have been using SharePoint List Adapters that we got from CodePlex long time ago. It works great in SSIS 2008. However we are trying to upgrade all of our jobs to run with newer version and using SQL Server Data Tools 2015. I installed SQL Server Data Tools 2015 on the same machine as SQL Server 2008 Developer Tools. I am still able to use the

问题 I would like to implement the following logic to my Lookup query as an expression: SELECT ID, CASE @[User::ConnectionStringID] WHEN 1 THEN "NE" WHEN 2 THEN "BALT" WHEN 3 THEN "NY" WHEN 4 THEN "PA" END AS Region FROM dbo.Table; My package is executed in a loop where the connection string is dynamically updated using a config file and it loops 4 times as shown in the above logic. I realized today that the Lookup transformation has no expressions available to it and I haven't been able to find

问题 I have VS2015 Community and SQL Server 2016 Developer installed. Using the MSFT link, I've ensured to download the latest version of SSDT, which appears to install without error (though, Integration Services do not show in the SQL Configuration Manager). Using previously validated projects that creates and executes SSIS packages, I cannot get the same code to work with the current setup. The error showing when I debug: Component: SSIS.Pipeline Error: To run a SSIS package outside of SQL

问题 I have a 2012 SSIS project that runs on SQL Server 2016. I have SSDT 2015 on both my dev machine and server. Everything works fine except for script tasks - I made a change to an existing script task and rebuilt and redeployed the project and I receive the following error: Script task uses version 15.0 script that is not supported in this release of integration services. To run the package, create a new script. I've tried the following: upgrading the project to 2016 creating a new script