1.3 trillion rows of log data just nuked our production db. Fucking data scientists!!!

This is awesome.. 😝

😂 sorry!!

You need a dB built for data science then....

@brettmoan preaching to the chorus brotha. I'm working on it. Wish me luck.

@superuser "but what if we need to look at the logs??" they said. "just add more hard drive space" they said. Smh.

@shigeru how can you ever add hard drive space on a device that's no longer supported? How can you make a device faster when the OS is archaic?

@rant burn it to the ground (insert magic here) and whala

Let me query that... Oops have been in the root section 😳

1.3 trillion? Only? The US debt databases have put up with 19 trillion. 😀

@rant you sftp the logs to a different server... You don't data doesn't need to reside o the application that created it when you are doing g analytics. The only (partial) exception would be if you NEED real time analytics. I preface that with partial cause you can get some pretty good "near real-time" analytics if you you just set up some automated replication jobs ( commonly in the form of etl batch jobs)