Posted on Monday, July 05, 2010 3:52 PM
I was inserting my datetime values from sql server 2000 to a column in a sql server 2008 database.
The result was:
OLE DB provider 'SQLOLEDB' could not INSERT INTO table '[...]' because of column '...'. The data value violated the integrity constraints for the column.
This was a not nullable field. Because there is (I verified this) always a filled field.
When I made it nullable, the insert processed with no problems.
And ALL the fields where filled with datetime values.
Is this a bug?
or am I missing a conversion here?