Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 13 Jun 2008 @ 13:48:11 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: Timestamp & six digit second
 
From:   Victor Sokovin

  But the last digit is *always* 0, 3 or 7, because the accuracy in SQL Server is only 1/300 of a second, so MS is just fooling the end user again :-)  


I asked our friendly DBA to run a few tests on Oracle / Windows server and it looks like it is able to provide 3 digits and the third one can be anything:

     13-JUN-08 01.50.12.147000 PM +02:00
     13-JUN-08 01.50.12.163000 PM +02:00
     13-JUN-08 01.50.12.179000 PM +02:00
     13-JUN-08 01.50.12.194000 PM +02:00
     13-JUN-08 01.50.12.210000 PM +02:00
     13-JUN-08 01.50.12.226000 PM +02:00
     13-JUN-08 01.50.12.241000 PM +02:00
     13-JUN-08 01.50.12.257000 PM +02:00
     13-JUN-08 01.50.12.272000 PM +02:00
     13-JUN-08 01.50.12.288000 PM +02:00
     13-JUN-08 01.50.12.304000 PM +02:00
     13-JUN-08 01.50.12.319000 PM +02:00
     13-JUN-08 01.50.12.335000 PM +02:00
     13-JUN-08 01.50.12.351000 PM +02:00
     13-JUN-08 01.50.12.366000 PM +02:00
     13-JUN-08 01.50.12.382000 PM +02:00
     13-JUN-08 01.50.12.397000 PM +02:00
     13-JUN-08 01.50.12.413000 PM +02:00
     13-JUN-08 01.50.12.429000 PM +02:00
     13-JUN-08 01.50.12.444000 PM +02:00
     13-JUN-08 01.50.12.460000 PM +02:00
     13-JUN-08 01.50.12.476000 PM +02:00

However, when he tried to get as many consecutive measurements as possible in a simple PL/SQL loop he observed that timestamps were changing in the following way:

     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.156000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00
     13-JUN-08 02.01.37.171000 PM +02:00

So, the true precision is probably not that obvious without further digging into the subject.

What can be said with certainty is that Oracle would give 6 digits on Unix (Solaris 10 in this case) without any problem (what these digits really are is a different question):

     13-JUN-08 02.08.53.072439 PM +02:00
     13-JUN-08 02.08.53.073025 PM +02:00
     13-JUN-08 02.08.53.073181 PM +02:00
     13-JUN-08 02.08.53.073305 PM +02:00
     13-JUN-08 02.08.53.073426 PM +02:00
     13-JUN-08 02.08.53.073545 PM +02:00
     13-JUN-08 02.08.53.073665 PM +02:00
     13-JUN-08 02.08.53.073783 PM +02:00
     13-JUN-08 02.08.53.073900 PM +02:00
     13-JUN-08 02.08.53.074017 PM +02:00
     13-JUN-08 02.08.53.074133 PM +02:00
     13-JUN-08 02.08.53.074249 PM +02:00
     13-JUN-08 02.08.53.074365 PM +02:00
     13-JUN-08 02.08.53.074482 PM +02:00
     13-JUN-08 02.08.53.074598 PM +02:00
     13-JUN-08 02.08.53.074714 PM +02:00
     13-JUN-08 02.08.53.074831 PM +02:00
     13-JUN-08 02.08.53.074948 PM +02:00
     13-JUN-08 02.08.53.075064 PM +02:00
     13-JUN-08 02.08.53.075180 PM +02:00
     13-JUN-08 02.08.53.075297 PM +02:00
     13-JUN-08 02.08.53.075417 PM +02:00
     13-JUN-08 02.08.53.075535 PM +02:00
     13-JUN-08 02.08.53.075651 PM +02:00
     13-JUN-08 02.08.53.075767 PM +02:00
     13-JUN-08 02.08.53.075886 PM +02:00
     13-JUN-08 02.08.53.076002 PM +02:00
     13-JUN-08 02.08.53.076118 PM +02:00
     13-JUN-08 02.08.53.076234 PM +02:00
     13-JUN-08 02.08.53.076350 PM +02:00
     13-JUN-08 02.08.53.076466 PM +02:00
     13-JUN-08 02.08.53.076591 PM +02:00
     13-JUN-08 02.08.53.076708 PM +02:00
     13-JUN-08 02.08.53.076824 PM +02:00
     13-JUN-08 02.08.53.076941 PM +02:00
     13-JUN-08 02.08.53.077057 PM +02:00
     13-JUN-08 02.08.53.077174 PM +02:00
     13-JUN-08 02.08.53.077291 PM +02:00
     13-JUN-08 02.08.53.077406 PM +02:00
     13-JUN-08 02.08.53.077522 PM +02:00

Victor



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016