Post reply

SSIS execution from .net

  • February 24, 2011 at 7:55 pm

    #388932

    I need to create some SSIS packages. My source will be delimited text file,xls file,xlsx and csv files.

    The files can have 100 to 500,000 rows and each row can have 8 to 19 columns.

    I know how to create SSIS packages using these files and then to import data into the DB tables.

    But the application developer need to run these packages from the application and before he execute the package he will have to validate the data( for data type matches and string length,email address validation etc...)

    So what additional steps I should other than just creating SSIS packages?

    AND what parts Can I cover as a database person?

    Thanks.

  • February 24, 2011 at 7:56 pm

    #1291346

    database is sql 2008 with .net 4

  • February 27, 2011 at 3:27 pm

    #1292080

    I am still looking for some help on this. If anyone can answer this I would be very greatful.

    Thanks.

  • February 28, 2011 at 2:04 am

    #1292189

    Why does the data validation needs to be done upfront?

    Can't you do it in your SSIS packages?

    Or another approach:

    If the .NET guy already reads everything to validate the data, he can just as easily write it to the database. No need to read it twice.

    (you can also incorporate .NET in the SSIS packages, so you guys can also nicely work together :-))

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • February 28, 2011 at 2:18 am

    #1292191

    SSIS needs to be installed on any machine running the package - so the app cannot just initiate the package to run unless you have SSIS installed everywhere (sounds expensive!)

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • February 28, 2011 at 5:28 am

    #1292238

    Hi,

    I believe the best way for this approach is applicative (meaning in C#).

    You can make in C# the check of the data and to put the data into a DataTable

    Afterwards you can use the SqlBulkCopy class to make the correct mapping to the database structure definition and just make the Transfer.

    This has no need of SSIS.

    if you want SSIS to be involved you can run over some folder that has the files and pass them through as arguments to C# executable program.

    Good luck,

    Michael Bogatin.

  • February 28, 2011 at 5:41 am

    #1292243

    mish_b20 (2/28/2011)

    Hi,

    I believe the best way for this approach is applicative (meaning in C#).

    You can make in C# the check of the data and to put the data into a DataTable

    Afterwards you can use the SqlBulkCopy class to make the correct mapping to the database structure definition and just make the Transfer.

    This has no need of SSIS.

    if you want SSIS to be involved you can run over some folder that has the files and pass them through as arguments to C# executable program.

    Good luck,

    Michael Bogatin.

    I can just as easily turn it around and say that it is all possible in SSIS and that there is no need for C#.

    It all depends how you look at the problem I guess 🙂

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • March 3, 2011 at 7:49 am

    #1294026

    Thanks Guys.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply