Hi guys,
Ok I haven't really done SSIS. I used Visual Studio 2005 to create the package and when I run it it exports data from a SQL Database into a Access Database. This works just fine. On success/fail an email is sent to me.
Every night the records in the access database will be deleted and a new export will begin. I can't really amend any data because there's no date field to use (maybe there's a work around.. not sure)
But it's fine for me as is.
Problem that I have is:
When I run the SSIS within visual studio every works fine. When I create a JOB in SQL and use my SSIS (File system or Server) then it runs and it executes 100% according to SQL.
When I check my access database nothing has been changed. No data was deleted or added. So why doesn't the SSIS work in SQL Jobs?
Thanks
Ok I haven't really done SSIS. I used Visual Studio 2005 to create the package and when I run it it exports data from a SQL Database into a Access Database. This works just fine. On success/fail an email is sent to me.
Every night the records in the access database will be deleted and a new export will begin. I can't really amend any data because there's no date field to use (maybe there's a work around.. not sure)
But it's fine for me as is.
Problem that I have is:
When I run the SSIS within visual studio every works fine. When I create a JOB in SQL and use my SSIS (File system or Server) then it runs and it executes 100% according to SQL.
When I check my access database nothing has been changed. No data was deleted or added. So why doesn't the SSIS work in SQL Jobs?
Thanks