Timeline for Timeseries: SQL or NoSQL?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot | replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/ | |
| Feb 5, 2016 at 17:20 | comment | added | Roman Pokrovskij | May be this is a good solution but the real "time series" application should support "zoom into data" functionality, and there database can't help with that. Time series databases are more about clever "zoom in" and "zoom out". | |
| Nov 8, 2011 at 8:02 | comment | added | Nicolas | While the DBA consultants work on targeting a beefy SQL Server installation, I will go ahead with testing with a BigData setup. | |
| Nov 8, 2011 at 8:02 | vote | accept | Nicolas | ||
| Nov 8, 2011 at 8:01 | vote | accept | Nicolas | ||
| Nov 8, 2011 at 8:01 | |||||
| Nov 8, 2011 at 8:01 | comment | added | Nicolas | Thank you very much for your answer. You've raised some very valid points. I completely agree with storing in UTC. I'm enforcing the idea that all data is delivered to the frontends (web, desktop & mobile) in UTC. We have multinational customers, and the OS should be responsible for doing the time conversion. I have a DBA company working on our entire data set, and wondered what others would come up with. Thanks again. | |
| Nov 7, 2011 at 18:35 | history | answered | Pursuit | CC BY-SA 3.0 |