SSMS vs DBeaver vs DataGrip?
I still use SSMS for SQL Server because, well, it’s SSMS. It’s not pretty, but it’s reliable and does what I need.
For multi-database work, I usually see people split between DBeaver and DataGrip. DBeaver is open-source and covers a lot for free, which is hard to argue with. DataGrip feels stronger when you write a lot of SQL and want the editor to stay out of your way.
So my current setup is basically SSMS + one “universal” database tool, depending on the project. Has anyone here actually moved fully to one tool and stayed loyal, or does everyone keep a slightly embarrassing toolbox too?
u/MatynDev — 4 days ago