Do we need to use ssms if visual studio already has sql server?

Question

Just like the title, why do we need to use ssms if visual studio (2019) already has sql server?

I am just starting to EXLPORE MORE about databases (.mdf) in c# (specifically for standalone desktop apps) and try to make them secure, as I am doing my searches I stumbled upon SSMS. I don't even know if SSMS is "necessary" since I can just create a service-based database and do the queries there. I have also deployed a desktop app to client machine with just service-based (.mdf) database (without ssms).

As you can see in this image, I'll just go to Server Explorer and then I can just do database stuff right? create tables, stored procedure, functions, etc.

I can also go to SQL Server Object Explorer to do some database stuff that ssms can do. Like logins, server roles etc.

Can someone please enlighten me about the importance of using ssms? or why do we even need it?

If I watch youtube tutorials about CRUD, most of them is using ssms, and I don't, I just add a service-based database and it just works.

Edit: Thank you for everyone who commented and even answered in my post, but I have found this helpful website that really enlightened me about the difference of ssms and vs(for sql).

Based on Grant Fritchey's Answer:

As to point four, are you developing code and databases? You may see better use in VS (source control being the biggie here). Are you managing servers and databases as well as developing code and databases? You may see better use in SSMS.

For now, I'm just going to stick with VS since it all fits my needs and I am still not managing servers like a system admin.

question from:https://stackoverflow.com/questions/65884893/do-we-need-to-use-ssms-if-visual-studio-already-has-sql-server

Answer 1

Every thing that you can do within SQL Server can be done through code. Yeah, you'll need at least two languages, one to manage the OS & SQL Server service, and the other, T-SQL, to manage all the rest. However, no GUI of any kind is needed. Everything can be done through the code.

With that in mind, which code editing software do you like? Visual Studio? Awesome. Go write code.

Now, fact is, not all of us can memorize every single bit of T-SQL needed to manage a system from soup to nuts. So, we use a GUI to make things easier. The VS GUI does some things to assist writing CRUD statements, creating some structures, stuff around the management of the internals of a single database. The SSMS GUI on the other hand, does all that, then a ton more, focused on servers, instances, databases, and pretty much everything necessary to manage SQL Server. It has tools built in to help you set up Availability Groups, consume Extended Event data, manage security, backup databases, restore databases and more. None of this is available through VS.

So, the GUI is just a tool.

Do you need a philips head screw driver? There you go, Visual Studio. Do you need a scientifically calibrated impact wrench? There you go, SQL Server Management Studio. These things are just tools. Use the right tool for the job.