Question

Quick intro to the existing process: an SSIS foreach loop imports a flat files into a SQL Server table by looking for any text file in the entry path folder, after the import, it dumps the flat files into an archive folder. This happens with a total of four flat files and since it’s only looking for any text file, it has no problem.

However, the new idea presented was instead, SSIS should run a process which first captures the date and State off of the text file (from the file name, not inside the file), then insert the data into SQL Server along with the State and date, which was captured, then archive the files. The idea behind this was that if a date was a month behind or ahead, SSIS wouldn’t import the file (or if the year was wrong, it wouldn’t import it).

So now
– SSIS first needs to check to see if four files exist.
– If four files exist, then it moves into the foreach loop (at least, I’m guessing this would be the best way to approach this problem).
– In each loop, a process needs to parse the date and State from the file name and it needs to import the data into SQL Server, adding the date and State parsed into the appropriate columns.
– Then it needs to archive that file and move on to the next one.

I’ve never done any parsing, and I tried playing around with expressions and connection strings to search for the current month and year, but no luck.

(Finally, I know very little C#, so script tasks are out of my league).

Answer 1

Forgot to post my solution: without using any C# or VB, I found a way to insert the name of the file into a table and parse the file name using TSQL. Using an “Execute SQL Task” you can use the SQL statement below this:

INSERT INTO Table VALUES (?)

With a string variable for the project set to be the current file’s name, you will set that under “Parameter Mapping.” From there, you’ll have the full file name in a SQL table and can parse it.