SQL server 2014 in VS 2013 - Develop 3 different types of packages and maintain them efficiently

Question

Hello Everyone,
I’ve been assigned a task to develop 3 different SSIS packages.
Package 1 – There will be roughly 50 CSV files, I need to read them one by one and create a new database and a table per CSV file in SQL 2014.
This will be a one-time job.
Which is the best option in SSIS package to create database and tables in SQL 2014? I assume I need use “Execute Script Task” here, although please advise.
Package 2 – This will run on daily basis. It will again read those 50 CSV files one by one and migrate their data to tables.
Also, out of 50, couple of files (the exceptional file names have to be configured somewhere as client might add some more files for it out of 50) needs to be treated in different way.
For them the tables have to be truncated first and then insert data into them.
Which is the optimal and fastest way to move such data from these files to SQL tables? Can I run the parallel job in for each loop container?
Where should I configure such “no ordinary” file names?
Package 3 – This job will run once a six months. It will basically perform a purge for the data.
This needs to be parameterized where client can set-up a cut-of-date for it and it will delete the data from all these 50 tables at SQL server.
How to allow a client to insert the cut-of-date?
What is the optimal option to read all tables of database (50 tables) and perform purge based on the cut-of-date?
Common question:
Where should I keep the path for the folder from where I need to pick the CSV files?
How should I deploy and schedule package 2 and 3?
Can anybody please advise what are the efficient/standard ways to maintain such packages?
Any help on this would be greatly appreciated.
Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com

Answer 1

You can create a Table in your Database to store all folder path and/or other parameter values (i.e. Error
File Path, Export/Archive file folder path, email address for notification, SSIS catalog deployed folder/project name etc). 
For Project deployment: Deploying
the Lesson 6 Package
After deploying the project, use SQL Agent to schedule Scheduling SSIS packages
with SQL Server Agent
web: www.ronnierahman.com