There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
SSIS - Import Excel Task Running Fine in Visual Studio, Failing as a SQL Job
Morning All,
I'm having difficulty with a package I have created to import an Excel Spreadsheet into a SQL Table.
Basically we have an aged Call System that doesn't have an ODBC setup for exporting Call Stats information, however it is able to export the information into a CSV format and email out.
I have created a VBA Process in Outlook that saves said file to a folder upon it being emailed out. I have then created an SSIS Package that takes whatever file is in the directory and imports it into SQL.
This works without issue in Visual Studio and then Executing the package using the debugger, however when the job actually runs in SQL Server Agent the job states it completes successfully however the file remains and doesn't import (the file is supposed to be deleted at the end of the SSIS Package.)
Anybody able to shed some light on this for me.
Cheers.
I'm having difficulty with a package I have created to import an Excel Spreadsheet into a SQL Table.
Basically we have an aged Call System that doesn't have an ODBC setup for exporting Call Stats information, however it is able to export the information into a CSV format and email out.
I have created a VBA Process in Outlook that saves said file to a folder upon it being emailed out. I have then created an SSIS Package that takes whatever file is in the directory and imports it into SQL.
This works without issue in Visual Studio and then Executing the package using the debugger, however when the job actually runs in SQL Server Agent the job states it completes successfully however the file remains and doesn't import (the file is supposed to be deleted at the end of the SSIS Package.)
Anybody able to shed some light on this for me.
Cheers.
Asked:
1 Solution
You might check the allowable errors in your package, and consider running the sql agent job with a proxy with credentials that has permission to the directory your modifying.
Hi,
which SQL Server version are you using?
Which CPU architecture?
When running a package in VS / BIDS it will be executed as 32bit, depending on your installation the SQL agent job might run with 64bit where you will not have the Excel ODBC connection drivers.
To log a little bit more details, just configure the execute package step in your SQL agent job by
- adjusting the commend line to include "/REPORTING EWCDI
- in the "Advanced" properties to "Include step output history" and write to a dedicated log file
HTH
Rainer
which SQL Server version are you using?
Which CPU architecture?
When running a package in VS / BIDS it will be executed as 32bit, depending on your installation the SQL agent job might run with 64bit where you will not have the Excel ODBC connection drivers.
To log a little bit more details, just configure the execute package step in your SQL agent job by
- adjusting the commend line to include "/REPORTING EWCDI
- in the "Advanced" properties to "Include step output history" and write to a dedicated log file
HTH
Rainer
Hi,
Thank You Very Much Both.
Rainer that was spot on enabling the Step Output History and getting a detailed log pointed me in the direction of a variable that was being populated with a datetime and it was a 'string' type.
I amended this and run ran and this ran perfectly, surely with an error being outputted though the package should fail and not succeed?
Thank You Very Much Both.
Rainer that was spot on enabling the Step Output History and getting a detailed log pointed me in the direction of a variable that was being populated with a datetime and it was a 'string' type.
I amended this and run ran and this ran perfectly, surely with an error being outputted though the package should fail and not succeed?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
After checking the file path you decide file is going to load or not. If not then create dynamic filepath variable.
To track these enable the SQLLogging in SSIS package and check sysssislog table on msdb database.