Hello juventusaurabh ,
In my opinion this is the wrong way to go. Why do you need to create a package
programmatically from scratch? Is this a one time operation or is this every
time?
The problem is that you are going to build a package and then run it. Whilst
this will give you maximum flexibility it will also cost you in effort.
I like the idea of being able to call a package from C# and manipulate properties
in an existing package from C# I am just unsure as to why I would want to
build a package very time from scratch and then execute it.
I guess if I need to do that then maybe doing the whole extract/import routine
in C# would be less costly.
You have changed the subject of this message.
Why not move the data to SQL Server (Staging tables) and then run some scrubbing
routines in TSQL to check the validity of the data before inserting. None
of this requires C#. What part of the package would need to be done using
..Net?
Data scrubbing becomes a lot better in SSIS.
Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Quote:
Thanks ppl for your help.
I actually need to create a DTS package runtime, add tasks to it (to
convert text file to sql table) and validate the data in tables.
Can anyone plz help me with runtime creation of package in C#.Net
Thanks |