A moment shown by the product is shown in UTC, and the column says so: "Started (UTC)" in the [[Invantive Query Tool/Connection Monitor|Connection Monitor]], "Time (UTC)" in the [[Invantive Query Tool/Trace|Trace]] panel. ## Why Not Local Time A statement runs against a platform in another country, from a workstation in a third, and is looked at afterwards by somebody in a fourth. Every one of them reading "20:08" as their own clock means four different moments, and comparing a trace with the log of the platform then fails on an hour nobody can find. One zone, named, is what makes the comparison possible. Summer time makes it worse rather than better: an hour which occurs twice a year and one which does not occur at all are not a good foundation for "which of these two calls came first". ## What This Means When Reading - A moment in a panel is UTC. Local time is UTC plus the offset of the day in question, which in the Netherlands is one hour in winter and two in summer. - A moment in the data of a platform is whatever that platform stores, which is often local and sometimes without a zone at all. The product does not silently convert it. - A date without a time - an invoice date, a period - is a date and carries no zone. It is not shifted. ## In a Statement The functions for the current moment, for converting between zones and for formatting a moment as text are documented under [[Invantive UniversalSQL/Invantive UniversalSQL|Invantive UniversalSQL]], with the format masks under [[Invantive UniversalSQL/General/Format Masks|Format Masks]]. A comparison between a column of a platform and "now" is worth writing carefully: which of the two is UTC, and which is local, decides whether the answer is right or an hour out. Reading the column in [[Invantive Query Tool/Describe Object|Describe Object]] says which type it is and therefore which of the two it holds.