October 25, 2011 at 7:24 am
I have a 2008 SSIS package that works fine in BIDS but fails when I run it in the scheduler.
It is just an import package.
I truncate the table and import a text file.
I want to overwrite the table each day.
When I run the job in SQL Server Agent I get this error:
"There is already an object named 'TableName' in the database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
It works as desired in BIDS.
Indeed the table does exist, I don't want to recreate it, just truncate it and insert all the records in the file.
Any ideas what may be incorrect? Thanks in Advance.
October 25, 2011 at 8:06 am
Try this link. It worked for me.
October 25, 2011 at 8:45 am
Thanks for your response.
I do not believe my issue is permissions based.
I did try a proxy account and got the same error.
Good idea to try that, thanks. (especially since it works within BIDS)
Pretty sure my issue is the table already exists and the package is trying to create it.
I thought using an insert query (not Select Into) would work.
I didn't really want to drop the table but I guess I could try that instead of truncating it.
October 25, 2011 at 9:23 am
Nevermind.
It helps when you chose the correct package to run.
I'd picked an old version in the the SQL Agent job. DOH!
Thanks
October 25, 2011 at 9:41 am
Have you traced it to see what is actually being sent to the database?
CEWII
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy