Question & Answer
Question
In DB2 UDB for Linux/Unix platforms, the "CURRENT TIMESTAMP" special register can return a timestamp with a precision of microseconds. For example, db2 "values (CURRENT TIMESTAMP)" 1 -------------------------- 2010-06-20-16.53.34.392348 However, in Windows the last 3 digits representing microseconds in the returned timestamp are always 000. db2 "values (CURRENT TIMESTAMP)" 1 -------------------------- 2010-06-20-15.42.04.578000 Therefore why in DB2 UDB for Windows platforms it can only have precision of milliseconds?
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"OTHER - Uncategorised","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1","Edition":"Enterprise Server;Express;Personal;Personal Developer\u0027s;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21438229