This content has been marked as final. Show 3 replies
The SQL Server table I used to reprot the issue at our SQl Dev team is:
drop table DateTimeMig;
create table DateTimeMig ([modificationDatetime] [datetime] NOT NULL default getutcdate());
And I reproduced with 3.1 the migration code issue:
-- DROP TABLE DateTimeMig CASCADE CONSTRAINTS;
PROMPT Creating Table DateTimeMig ...
CREATE TABLE DateTimeMig (
modificationDatetime DATE DEFAULT SYS_EXTRACT_UTC NOT NULL
Issue is investigated by migration developer team.
Edited by: kgronau on Feb 29, 2012 11:40 AM