数据流任务成功执行但未将任何行写入 Excel 文件

Question

I am working on SSIS package that is fetching data from SQL server and inserting into Excel file... in Data Flow Task i've used OLE Db source and Excel destination .

After configuring OLE Db source i can preview the resulting row and even data flow task executing successfully without giving any error.. but not inserting any row..

Answer 1

Well fortunately i found the answer,I did two things..

1. I just deleted the old Data Flow Task on which i have tried so many different settings and parameters... and Build the Data Flow Task all over again...

2. In SQL query i'd wrote the Fully qualified name instead of 'Use Database' Statement.

Hope this will help someone..

Answer 2

Have you tried writing to a flat (text) file first to be certain that data's coming out of your data flow task and going into the results?

Be absolutely sure that you've mapped the columns from the source to the target as well.

Answer 3

Here's a clear explanation what's going on. Most likely, you are using table variable... SSIS OLE DB Source Using Table Variables Returns No Rows

Answer 4

My issue was a print statement in the SQL command. I commented it out and it worked. The preview worked with the print statement in there. Tricky...

Answer 5

I already had SSIS package that was running well and writing to file properly. I changed the query and it stopped writing anything in text file even though i have records which i can see in preview. Solution : Sometimes you have query that has USE database command before the query begins.. remove that command and it will work. Hope it helps someone. Cheers.

Answer 6

I needed to choose the Connection Manager node in my Data Flow Task and set the ConnectionString property with the name of the file I wished to create; without this field filled out, no file appeared.

Answer 7

I find if I reopen my script component and select "run code analysis" it does a slower 'rebuild all' (Visual studio 2017) which 'wakes it up' again and then the rows are processed. Overall though SSIS/VS 2017 is a nightmare with memory errors, crashes which wipe out the whole csproj and folder structure. I have had to recreate the project dozens of times.