SSIS value is not in expected range by OLE DB Datasource
I am using Visual studio 2013 update 3 and my colleague with update 4 each installed. We are using dools data for SQL Server 2014.
I created several DTS packages that my college updated while it worked without issue. But all of a sudden I get a "value is not in the expected range" warning from the data source and cannot edit the columns there .... I needed to recreate the data source for the message to disappear again.
My question here is that the cause of this issue is the extra columns appearing in the table that the data source has accessed. (I've seen sync warnings for data when the target table gets new columns or orphaned columns, but this is the first time something has changed for the original table).
Or could this problem have a completely different cause?
source to share
It's been a long time since I was working on an SSIS project, but I do remember this error. My experience was that it was caused by the input metadata being outdated in a certain way, and what you call your suspicion matches that.
The solution I found to avoid this was very specific to all of my input components, choosing the exact columns I wanted rather than selecting everything. I think in the end I actually changed all of them to use hand-written SQL queries rather than the GUI column selector.
Also I don't remember if there was the same error, but the same: sometimes after changing the schema when trying to open a component the GUI would throw an error and not open, but when I tried again it would resolve the error.
Sorry, I couldn't be more definitive in my answer, but hopefully this information helps you in the right direction.
source to share
I used a simple method and it works fine. In the OLE DB source editor, when I kept the same connection manager, changed the data access mode (from table / view) to SQL command, and used the SQL command to select the required columns. The error message didn't appear anymore and I could see the column values ....
source to share