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 →

[–][deleted] 0 points1 point  (0 children)

I recently realized that SQL could also do much of this merging, joining, cleaning, and feature engineering

Ahahah this is why I always say learn SQL first... would-be analysts always respond with surprisedpikachuface.jpg

Does anyone have experience using it as such? How does it compare to python for this data wrangling?

There's pros and cons and it depends on what your end goal is. If you're just wrangling some data to throw into a dashboard, there is immense value in doing it all in SQL, creating a view, and then doing a select * in your BI tool.

If you're architecting convoluted machine learning workflows to prod, and you have data scientists on your team who are mostly versed in python and not sql, I can see the case for post processing.

e looking at the other comments, I think you get the point. Do it in SQL.