SSMS or SSDT

Question

SSMS or SSDT

Viewing 15 posts - 76 through 90 (of 97 total)

You must be logged in to reply to this topic. Login to reply

sihundleby SSC Enthusiast Points: 157 More actions · Answer 1

I use Management Studio primarily, but still use VS for Data/Schema comparison and creating deployment scripts.

bmmpt Grasshopper Points: 11 More actions · Answer 2

I have a huge list of stored procs in my database and I can't find a way to filter them in SSDT (or any other object type for that matter), so I'm sticking with SSMS.

Joe Kelly-8908 SSC-Addicted Points: 491 More actions · Answer 3

Mainly use SSMS to write SQL code, but have had a look at VSCode and it looks like it might be a runner.

JK

Tks,

JK

Rune Bivrin SSCrazy Eights Points: 8441 More actions · Answer 4

I'm gonna go all "Four Yorkshire-men" on this and comment that back in my day, we'd been glad for ISQL/W. We would use SAF in character mode and be happy! None of this "window" rubbish! 🙂

Just because you're right doesn't mean everybody else is wrong.

Rune Bivrin SSCrazy Eights Points: 8441 More actions · Answer 5

Evidently, I wrote much the same thing 4 years ago. 😛

This reply was modified 4 years, 10 months ago by Rune Bivrin.

Just because you're right doesn't mean everybody else is wrong.

jonathan.payne SSC Rookie Points: 28 More actions · Answer 6

jonathan.payne

SSC Rookie

Points: 28

June 17, 2019 at 7:52 am

#3654352

I have used SSDT but I live in SSMS.

nick.mcdermaid Hall of Fame Points: 3809 More actions · Answer 7

I use SSMS more. I would happily use SSDT more if it wasn't so flaky and crash prone!

a_duce Newbie Points: 1 More actions · Answer 8

I use both. SSMS for DBA tasks, SSDT for development tasks.

The reverse engineer/import db functionality in SSDT has been a huge time saver when starting work with neglected legacy db's; Being able to instantly see potential problems in the code (3 and 4 part references, broken queries, etc.) simplifies understanding and planning of architecture.

For running ad hoc queries and peformance tuning, SSMS is still king. For everything else, SSDT wins hands down especially with multiple deployment environments and multiple developers when integration with source control and continuous deployment/integration are necessities.

ed.elliott SSC Rookie Points: 43 More actions · Answer 9

It depends on the project, for new greenfield databases where we can can stop the rot before it sets in then SSDT - older projects that have "issues" i'd probably stick with ssms./azure devops and a migrations based deployment approach.

Aleksl-294755 Hall of Fame Points: 3514 More actions · Answer 10

Aleksl-294755

Hall of Fame

Points: 3514

June 17, 2019 at 11:23 am

#3654383

I use both, but prefer SSMS. It is more flexible.

Treehouse Ten Centuries Points: 1234 More actions · Answer 11

For us, SSMS and SSDT are different tools that serve different purposes. We use both, all day, every day.

We use SSMS for system administration and general server management. SSMS also excels in everyday querying and data investigations/analysis. In fact, we do almost all our development and (manual) unit testing using SSMS.

BUT, when it comes time to deploy code, it makes much more sense to use a tool like SSDT. Many have mentioned that it integrates well into source control and I agree it does so very well, but there are other capabilities we leverage within the tool (pre/post deployment scripts for example) that allow us to essentially deploy any version of our code to any version of our database.... at the click of an icon. That is a pretty big deal.

For years I had manually arranged scripts using SSMS (and its predecessors) carefully orchestrating the sequence of steps involved in a change/new version of our app, and this required a considerable amount of effort. SSDT takes care of that for us.

Our dev team couldn't live without either tool at this point. I do wish the easy of querying and server admin stuff was available within VS/SSDT so we'd only have to use one app. One can dream.....

mark.gelderblom Newbie Points: 1 More actions · Answer 12

Hi, use both but prefer SSDT as a Project in Visual Studio together with my SSAS, SSIS and SSRS projects.

One Solution to change them all!

Eric M Russell SSC Guru Points: 125522 More actions · Answer 13

I use Visual Studio or SSDT for SSIS package development and schema / data comparison. However, I find the UI too cluttered and AppDev centric for it to replace SSMS as my primary tool for SQL Server. I'm also looking at Azure Data Studio.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

kparchinski Newbie Points: 2 More actions · Answer 14

I use SSMS for all my SQL development; however, now that the Teams integration and debug options have been removed in version 18.x forward, I may need to start thinking about moving to VS.

ken.burch 31806 Newbie Points: 1 More actions · Answer 15

Even though I'm nearly always in Visual Studio, I still use SSMS for any serious database work. It's so much more complete, I can trace queries, check the query store and then change/test the offending SQL.