February 26, 2013 at 10:45 am
Hi I hope I am posting this to the correct forum.
I fairly new to SQL Server and SSDT so here goes.
I have a package that does the following steps:
1. File system task that delete a backup file.
2. File system task Renames the current file to backup file name.
3. File system task that copies a existing file that only has headers in it for the extract of the data for a view.
4. Dataflow task that inserts the data from the SQL to the Excel file in step 3. This is where the process breaks, the data is not inserted into the Excel file.
There are 4 more steps that do the same thing as steps 1-4 above the only difference is it is on different files in the same location as steps 1-4 and those 4 steps complete without any issues.
I am wondering if anyone has come across this problem before and how they resolved the issue.
BTW when I run the package from my local SSDT the process runs and works without any issues. The failure only happens when the package is deployed on the SQL Server.
If this isn't the right forum for this question. Please let me know the correct forum and I will be happy to post it there.
Thanks
NB
March 1, 2013 at 12:02 am
Define "breaks." Do you receive an error or does the package execution succeed but no data is present in the Excel file?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 1, 2013 at 6:31 am
Hi, thanks for asking the package succeeds with no error messages, but the data is not written to the excel file.
March 1, 2013 at 8:13 am
What does your logging say when run through SQL Server as compared to when it runs successfully through SSDT?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 2, 2013 at 6:34 pm
Thanks for the responses, we found this was a permissions issue. The issue has been resolved.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply