[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1140
  • Last Modified:

SSIS SQL Source to Excel Destination not writing any rows

Hello, I have a simple SSIS package that has two items in the data flow, OLE DB Source & Excel Destination.  They are connected and I get no errors when I run the package however, I do not get any data in the Excel spreadsheet.  Though the Execution Results says that 1 row has been written.  I have declared the first row in the Excel spreadsheet as the header row and it has the name of the columns in it.  I get one row as a result from my SQL Query which is fine.  But nothing shows up in Excel and I am completely lost at this point over it.  

Any ideas or suggestions as to what to look at is greatly appreciated.

Regards,
John
1
j_heck
Asked:
j_heck
  • 3
  • 2
1 Solution
 
Rainer JeschorCommented:
Hi,
which SQL version?
Could you zip the package and attach it to this question?
Thanks.
Rainer
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
>I do not get any data in the Excel spreadsheet.
Eyeball all of your Excel doc to make sure that is the case, as SSIS to Excel has some known issues where if a package previously inserted 100 rows, and you run it again, the output data will appear on row 101 and not row 1.
0
 
j_heckAuthor Commented:
I've requested that this question be deleted for the following reason:

I figured out what I was doing wrong.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
>I figured out what I was doing wrong.
For the benefit of future experts in your situation, spell out what you were doing wrong here.
0
 
j_heckAuthor Commented:
You are right Jim, I apologize for not giving the resolution.  It was a file naming problem with the file it was being written to in the Excel Destination.  The incorrect sheet was being written to.  This was still giving me problems so for the time being I switched it tow write to a CSV file using the Flat File Destination and the Flat File Connection Manager.
0
 
j_heckAuthor Commented:
Jim you got me looking more closely at the Excel Destination and I did switch to using a Flat File Destination for the time being.  Thanks.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now