I'm currently updating all of our ETLs using Visual Studio 2015 (made in BIDS 2008) and redeploying them to a new reporting server running on SQL Server 2016 (originally 2008R2).
While updating one of the ETLs I got this error:
Exception from HRESULT: 0xC0202009 Error at Load Staging Table [OLE DB Source [129]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Invalid object name 'dbo.TimeSheets'.".
Here's what I've tried:
I got a successful fix from the comments of the question "The other option would be to fully qualify the table name {database}.{schema}.{table}
to ensure that, regardless of the default catalog, you query the correct database."
I was using some other database and it was caching and using that DB name rather than the new one I changed to.
I encountered the same issue - my Database was somehow, not getting picked up. So I manually added the database and test the connection and now it works fine.
For SSIS - Specially it is observed if any table name is coming as "Invalid object name" then Check as - First - Check table exist through SSMS and if not then SSMS> Edit > IntelliSense > Refresh Local Cache
Second - While making DB connection via "Connection manager" or already exist then - check table name comes in drop down of "Name of the table or View"
I tried several of the above suggestions but what worked for me in the end was the good old close and re-open of SSDT!
User contributions licensed under CC BY-SA 3.0