Hi there,

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.

2. I think I can help you more with this: The DB was imported from SQL Sever 2005. The tables that have this problem have the following behavior: They have a primary key declared, but also in the indexes list, they have a unique index with the same name as the primary key index.

For instance when I create the table completely from within DDT the indexes list is:

which is correct. But when I import from the DB the indexes is like this:

Saving this table's structure will give me the exception. There are some tables that were imported and don't have that problem, and the indexes list is like this:

I could sent you a backup of my DB and also my SF DB if you like.

3. This exception comes from time to time, when I see it again, I will send you screen-shot.

Thanks Ben...

I think the info you gave me is enough information; I should be able to reproduce it from this... it certainly points me in the right direction.  Thanks.