Scripting a table with an ANSI default constraint of CURRENT_TIMESTAMP gives non-ANSI getdate() in the script - by John Paul Cook

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781321 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/13/2013 6:18:32 PM
Access Restriction Public


If you use DEFAULT CURRENT_TIMESTAMP when creating a table, when you use SSMS to script the table, the script contains the non-ANSI getdate() instead of the ANSI CURRENT_TIMESTAMP.

If I go to the trouble of creating a table with ANSI compliant syntax, I expect the scripting tool to generate ANSI compliant code when I tell it to script the object I just created.
Sign in to post a comment.
Posted by SAinCA on 8/6/2013 at 4:08 PM
Yet another "will not fix in the current or future versions of SQL Server" for a basic deficiency. I.e., this will NEVER be fixed.


Is ANSI compliance, therefore, something MS will ignore and we should NEVER look for?

Any comments on ANSI from the MS Team, please?
Posted by Ajay [MSFT] on 8/6/2013 at 2:21 PM
Thanks for reporting this issue. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server.
Thanks again for reporting the product issue and continued support in improving our product.

Ajay Jagannathan
Senior Program Manager
Posted by Microsoft on 3/15/2013 at 9:13 AM
Hello John Paul Cook. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (
Posted by John Paul Cook on 3/13/2013 at 6:33 PM
It also occurs on SQL Server 2008 R2.