SSMS or SSDT

Question

Post reply

SSMS or SSDT

Steve Jones - SSC Editor

SSC Guru

Points: 736494
More actions
March 27, 2015 at 12:00 am

#306168

Comments posted to this topic are about the item SSMS or SSDT

Viewing 15 posts - 1 through 15 (of 97 total)

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

badOedipus SSC Veteran Points: 202 More actions · Answer 1

badOedipus

SSC Veteran

Points: 202

March 26, 2015 at 10:51 pm

#1786739

Used both, prefer SSMS.

Christopher Reed Mr or Mrs. 500 Points: 510 More actions · Answer 2

I use both, but I've probably been using SSDT since I'm doing more with SSRS.

Christopher Reed, MCT, MCSD, MCPD, MSpec, MTA, MCTS
"The oxen are slow, but the earth is patient."

Gary Varga SSC Guru Points: 82166 More actions · Answer 3

Historically I have used both but SSMS substantially more (even in the time frame when they both have existed).

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!

shillbot SSC Journeyman Points: 82 More actions · Answer 4

I'm primarily a C# developer (with a heavy DB focus), and I spend most of my time in Visual Studio, but I find SSMS more comfortable for DB work (with an add on or two).

Phil Parkin SSC Guru Points: 246987 More actions · Answer 5

I use both.

In a shared environment (multiple devs to one DB) I find SSMS works better than SSDT.

But if you can get to the point where you do your dev on a local instance, SSDT is my preferred environment. The ability to build and publish is very cool and integration with source control works better.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

P Jones SSChampion Points: 12361 More actions · Answer 6

Management Studio open all day for database management and sql querying then either Visual Studio 2008 for SSIS/AS/RS development as we're on SQL 2008 for those or Visual Studio 2010 for ASP.NET development.

Gary Varga SSC Guru Points: 82166 More actions · Answer 7

My emphasis:

Phil Parkin (3/27/2015)
...SSDT is my preferred environment. The ability to build and publish is very cool and integration with source control works better.

Good point.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!

Alan Burstein SSC Guru Points: 61141 More actions · Answer 8

others bemoan the demise of isql/w

Yep. I was one of those people. This thread brought back some memories.

I do all my SQL in SSMS. SS%S happens in Visual Studio.

"I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

-- Itzik Ben-Gan 2001

Sue Callaghan SSC Enthusiast Points: 196 More actions · Answer 9

I use SSMS almost exclusively.

Used to use Enterprise Manager and ISQL but don't really miss the latter much!

Cheers,

Sue

SebastianCrewe SSC Rookie Points: 48 More actions · Answer 10

My work involves both maintenance/enhancement of existing databases and the creation of wholly new databases. For the former, I'd most likely use SSMS since it is easier to experiment on views and procedures there. For a new database, my preference is for SSDT.

SSDT offers easier methods for linking to source control (Ankh to Subversion), the more so since not all the developers here have the Red Gate toolset (including SQL Source Control). I also find the table scripts made in SSDT are more appealing - as well as the table definition, all foreign keys, constraints, triggers and permissions are in the one script. The use of variables in an SSDT project means that I can deal with environment-specific users in a generic way. I can also have several related databases in a single solution (eg Staging and Warehouse).

Sebastian

Erwin Oosterhoorn SSCrazy Points: 2320 More actions · Answer 11

I work with creation of new SQL code as well as maintenance, and due to the different servers and versions I use SSMS almost exclusively.

but also use Enterprise Manager as this is still on some of the servers we have to work with.

Health care is not one of the areas where a lot of money is available for upgrades.

Rune Bivrin SSCrazy Eights Points: 8537 More actions · Answer 12

ISQL/W... Pftt! New-fangled stuff.

I remember when I did most of the work in SAF on SQL Server 1.1. Those were the days...

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

Todd Townley Ten Centuries Points: 1320 More actions · Answer 13

Never tried SSDT, so SSMS exclusively. For one thing, it doesn't require the additional Visual Studio install if essentially all your work is directly in the database.

Daniel Parkinson Old Hand Points: 300 More actions · Answer 14

I mostly use SSMS. I do like SSDT when creating a new database, and also try to use it to keep the deployed version of the DB linked to version control.