![]() This means for a DATEPART of SECOND, you get 4.3 billion seconds on either side, which works out to "anchor date ± 136 years." Similarly, 2 32 milliseconds is ≈ 49.7 days.ģ If your data actually spans centuries or millenia and is still accurate to the second or millisecond… congratulations! Whatever you're doing, keep doing it.Ĥ If you ever wondered why our clocks have a 12 at the top, reflect on how 5 is the only integer from 6 (half of 12) or below that is not a factor of 12. 4 As a counterexample, grouping results into 13-minute or 37-hour bins will skip some :00s, but it should still work fine.Ģ The math says 2 32 ≈ 4.29E+9. Your query will be totally unreadable, but it will work.ġ If you want all :00 timestamps to be eligible for binning, use an integer that your DATEPART's maximum can evenly divide into.
0 Comments
Leave a Reply. |