4 ms·
I see this tool most useful for people who need to interact with multiple types of databases on the regular. If you only using SQL Server, SSMS is probably the
by hnrodey 11y ago
I see this tool most useful for people who need to interact with multiple types of databases on the regular. If you only using SQL Server, SSMS is probably the best tool for that. But if you have to use SQL Server, MySQL, Oracle, etc. throughout your day then a single tool is probably going to be the best option for you.
- alimbada 11y agoI don't know how Jetbrains DataGrip compares to SSMS, but on its own, SSMS isn't good enough in my opinion. With Redgate's [expensive] plugin (SQL Prompt, I think?), sure it's a fantastic experience. However, if you're paying through the nose for SQL Server licenses which come with SSMS Professional, it shouldn't be too much to expect the kind of functionality SQL Prompt comes with built in as standard in SSMS.
- klausjensen 11y agoI am curious... What you are missing from SSMS modern versions, that is so much better? The intellisense/code completion is very good in SSMS, as long as you are on modern versions of SSMS/SQL Server.
- hnrodey 11y agoSSMS isn't "good enough"? No offense but I think that is hogwash. SSMS is a fantastic tool and blows away anything I've used in the past. Short of refactoring support (which would be great), I SSMS is a tremendous tool.
- martinknafve 11y agoI assume there are several examples of this where there will be a better client for database X than to use this. I rarely use my swiss army knife - if I want to do something serious I use a real saw, screwdriver etc, because while the Swiss army knife may have a lot of features is pretty bad at all of them. I often see examples of Swiss Army Knifes software which integrates poorly with several different systems and good with none.