I have seen this problem in another topic, but there was no answer mentioned there.

When trying to deploy a data package for a table with a timestamp column, I get the exception:

SqlException: Cannot insert an explicit value into a timestamp column. User INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.

It seems like the DDT is trying to copy the timestamp values taken from the original table, while it shouldn't, since timestamps are updated by SQL server.

Did you come up with a solution for that?

Thank you.

OK...I see what happened I think.  This actually depends on how the data deployment package will package up the data.  If you rely on the data package to detect and include all children relationships as well, then yes, I could see how this could happen.  If you do not allow the data package to include the children within that deployment data item and you create an individual deployment data item for each of the children, then this may not have happened.  I will load you package and look at it to see if there is anything that could have prevented this, but that is probably what happened.