August 18, 2016 at 6:15 pm
Hello,
I'm using SQL Server 2008 R2 with SSIS. I have a stored procedure which loads a fact table, this table contains a column called "Average_Position". The procedure and SSIS package worked just fine until I removed a column called "Average_CPC" and then re-created the fact table to reload it. So now I have an empty fact table.
After I re-created the fact table, I tried executing the SSIS package and it fails on the step which loads the fact table. It's says that the field "Average_Position" does not exist. I checked the table in SSMS and it does exists. I've also checked sys.columns and it exists there, too. I've re-checked the stored procedure to be sure that the field is correct and that it's also pointing to the correct column during the insert. Everything is okay.
I've tried closing the SSIS package and re-opening, i've tried closing the solution, i've tried logging-off of the server - none of these things work.
I'm baffled. What could cause this issue and how the hell do I get around it??
August 19, 2016 at 1:25 pm
Hey folks - anyone have any suggestions? I'm dead in the water here. I looked at the XML code behind the package and that looks okay, i've restarted the server and I still get this error. When I execute the stored procedure on it's own, it runs just fine. I don't know WHY SSIS throws this error when I run it.
Clearly something is getting cached somewhere but I don't know where.
Any ideas?
August 19, 2016 at 1:30 pm
Check the mapping to the new fact table in your SSIS package.
August 19, 2016 at 1:45 pm
Setup package logging and what are the details of the error in the logs? When executing what type of task?
It seems like it might be a bit too vague for anyone to help you troubleshooting this.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply