I understand that you have found an answer to your question. This is for other users who might stumble upon this question. Here is one possible way of achieving this. Script Task can be used to find the list of files present in an FTP folder path for a given pattern (say *.txt). Below example … Read more
This worked for me: Install SSDT-BI for Visual Studio 2013. Open your solution in Visual Studio 2015. Select your SSIS Project in the Solution Explorer. In the Project menu select Properties. In the Property Pages dialog select Configuration Properties -> General Under Deployment Target Version change the Target Server Version to “SQL Server 2014.” Clean … Read more
Between your source and destination component, add a Lookup Component. Configure the Lookup to Redirect to No Match Output for unmatched rows. In your lookup source, write a query like SELECT T.PK1, T.PK2 FROM dbo.MyTable T where you only pull back the primary keys and then compare you input data to the target table’s. What … Read more
Just to give future visitors something to look on, in my case issue was I had two different version of SSIS installed on same machine. One was for 2005 and another for 2014. And oddly enough even I was explicitly pointing to newer version (as shown in later part of post) in my command, it … Read more
I know this is a late answer, but for anyone searching on this like I was, I found this to be the simplest answer: In the lookup connection, use a SQL query to retrieve your data and add UNION SELECT NULL, NULL to the bottom. For example: SELECT CarId, CarName FROM Cars UNION SELECT NULL, … Read more
For custom assemblies to be referenced and executed in Script Task, you have to add them to GAC. Here is an article with workflow. Alternative approach – provide your own AssemblyResolver in Script task code.
Taking a guess here while I wait on an answer to the comment, generally when a package runs fine in BIDS but doesn’t work from the commandline, I find it’s related to 64/32 bit incompatibility. Are you using Excel, Access or anything else that under the sheets uses the JET driver? That only works in … Read more
The way I have done this in the past is with an infinite loop package called from SQL Server Agent, for example; This is my infinite loop package: Set 3 Variables: IsFileExists – Boolean – 0 FolderLocation – String – C:\Where the file is to be put in\ IsFileExists Boolean – 0 For the For … Read more
I think you have almost got the expression correct except for the additional slash in the replacement string. Here are the expressions that might work for you. Expression #1: Removes all double quotes within a given string. REPLACE(COLA, “\””, “”) Expression #2: Replaces all double occurrences of double quotes with single occurrence of double quotes. … Read more
Indeed, limiting C# Script Tasks to language features of C# 4.0 brings the Debugger back to life. In my case, adding a single null-coalescing operator caused the debugger issue using Visual Studio 2015 (VSTA) on SQL Server/SSIS 2016. To restrict the Script to C# 4.0 we can enforce a specific Language Level in the Build … Read more