SSIS 2012 - OLEDB connection (Source) to Flat file (Destination)

  • Hello everyone,

    I'm trying to export the data from SQL database to Flat file.

    The data gets exported to the destination but it does not contain the header columns.

    Can anybody advise how to get the header columns in flat file?

    Thanks,

    Ankit

  • ankithimmatlalshah (4/10/2015)


    Hello everyone,

    I'm trying to export the data from SQL database to Flat file.

    The data gets exported to the destination but it does not contain the header columns.

    Can anybody advise how to get the header columns in flat file?

    Thanks,

    Ankit

    Hi and welcome to the forum.

    First a quick question, what have you tried so far or in other words, how did you do this export?

    😎

  • I've tried many things.

    Like deleing the destination and source components again.

    Check/uncheck the first column is data column

    Even when I tried to export the table from SQL server, it does not have the heading column.

    Unable to understand why am I not getting the heading row for all columns in flat file?

  • ankithimmatlalshah (4/10/2015)


    I've tried many things.

    Like deleing the destination and source components again.

    Check/uncheck the first column is data column

    Even when I tried to export the table from SQL server, it does not have the heading column.

    Unable to understand why am I not getting the heading row for all columns in flat file?

    In the Import Export Wizard, have you checked this?

    😎

  • I did that but still no luck. Please advise any other options.

  • ankithimmatlalshah (4/10/2015)


    I did that but still no luck. Please advise any other options.

    Can you tell us a little bit more about what you are doing,i.e. Source, Destination, Network etc.? Can you use BCP?

    😎

  • Is the source a table or a query?

    James Phillips
    Sr. Consultant
    Pragmatic Works

  • I just noticed you are using the import/export wizard which I have never had luck with working right. I have always had to edit the package afterwards and go into the destination and click the update button to update the text file definition.

    James Phillips
    Sr. Consultant
    Pragmatic Works

  • Hello,

    To resolve this problem, I had deleted the existing destination component, it's connection from connection manager and then I recreated the FL component from scratch. And surprisingly it worked.

    It seems like the same data connection for flat file component should not be used with multiple data flow tasks. Also, instead of selecting the existing file with Browse button, we should always create a new file.

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

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