4 ms·
I think it’s artificially presented as an exclusive option between sql and csv/nosql/whatever in data science. I know plenty of people who are comfortable in b
by prepend 7y ago
I think it’s artificially presented as an exclusive option between sql and csv/nosql/whatever in data science.
I know plenty of people who are comfortable in both. But I don’t know any “data science” people as good at sql as a good dba. But that’s ok.
I think a good analysis requires both sql and some flat file, if only for reproducibility. I’ve encountered many point in time analyses that can’t be recreated because they were just sql against db and there’s no way to reproduce the result months later. Are their methods accurate? Or auditable? It’s much harder because the source data is changed.
So I like talking about only-sqlers about the importantance of incorporating the data management of extracts and archives into the overall solution. And doing so in a way that doesn’t try to redesign the database trying to avoid the need for users to file away point in time snapshots of data.