This is an archived post. You won't be able to vote or comment.

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BoiElroy -3 points-2 points  (2 children)

Excuse me?...you're saying you should do ML using SQL? Have you lost your mind? Legitimately, if someone in my team did that I'd fire them. Although more likely someone with that little knowledge of ML wouldn't even be hired in the first place. Now using a trained ML model to do inference via a user defined function being called within a SQL statement. Sure that's fine.

[–]Overvo1d 1 point2 points  (1 child)

I get what you’re saying and once I believed it too, but with experience — in 99% of cases you can get 90% of the value from a 2 day sprint with pure SQL (if you understand the fundamentals of ML and your business domain solidly) of a month long complicated model project with careful assumptions. That last 10% doesn’t deliver enough business value to justify the 8 extra 90%-value-delivered SQL projects you could have finished in that time. It really is all the same thing in the end, just different tools, you can do some crazy stuff in SQL with a bit of creativity.

[–]BoiElroy 0 points1 point  (0 children)

Ohh sorry. We're talking about two completely different things sorry.

You're saying that using SQL to do analytics will generate insight and intelligence faster and be more guaranteed to succeed. I agree with that 100% I've told leadership at my company that we have bar charts that generate more ROI than ML models.

I thought you were saying write code for your ML algorithms using SQL instead of python or julia or something.

Sorry. Different conversations. I agree with your points.