problem exporting data from sql server to a txt or csv file

  • Hi!!

    I have a table with around 50 fields and when i am exporting data from that table to the txt or a csv file via DTS, the fields are not getting populated in the destination tab (in DTS). if i choose to pull only few fields i am able to see the field names in the destination tab. any idea why its doing this way.

    is there any limit in the number of fields to be used in csv or a txt file. please let me know.

    Thanks

  • Hi,

    I do not know of any limits in the number of fields usable. Even if there are, 50 fields cannot be a problem.

    I found on the other hand that some changes are not automatically passed on to the file when you have specified a connection to an already existing file. Then you may have to manually add the columns to your destination in the extended editor.

    If you want to have SSIS create a file with all fields then you need to obey a certain sequence when creating the destination, connection manager and connection to the last step processing your data.

    Then SSIS may create fields for each column and map them accordingly.

     

    Regards,

    Michael

  • Hi,

    i am using sql server 2000. I am doing this via DTS. i tried just giving 26 fields and it was able to read with no problems. so i am guessing that the number of fields matters for a txt or a csv file.

    Any ideas?

  • Hi,

    I just created an export to text DTS (with 62 columns by using the "Export Data..." wizard, and the DTS works correctly.

    Michael

  • Thanks Michael for your reply.

    I am able to do this via Import/Export wizard. I was using DTS designer to accomplish this and was facing problem. Thanks again for your help.

  • hi pinky,

    try using wizard and bywizard save your dts. then you can check the difference between the one realized by wizard and your one.

    i've exported table with more than 50 fields without any problem...

    Luciano

Viewing 6 posts - 1 through 5 (of 5 total)

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