Is it possible to migrate a solution from SSMS to SSDT?

Question

Is it possible to migrate a solution from SSMS to SSDT?

VoldemarG

Hall of Fame

Points: 3883
More actions
August 24, 2021 at 4:15 pm

#3923564

VS 2017, SQL Server 2016 and 2017, is it possible and or making sense to migrate a solution from SSMS to SSDT?
The main purpose is to incorporate large solutions with multiple files into TFS that SSMS is not supporting.
Likes to play Chess

Viewing 6 posts - 1 through 5 (of 5 total)

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

frederico_fonseca SSCoach Points: 16154 More actions · Answer 1

what type of files you talking about - if SQLProjs then SSMS works differently from Visual Studio and there is no straight migration.

Jeff Moden SSC Guru Points: 1004312 More actions · Answer 2

I don't use "solutions" in SSMS. They just seem to make life difficult. That's not a personal bit of experience, though. I never knew about them for the longest time and then I saw a demo about them and a lot of the issues about them. I dom't remember everything from the demo but I do remember what my resolve was at the end of the demo... "Yeah... I'll never use those".

With that in mind, what do you find useful about "solutions" in SSMS? I'm always willing to learn something new or different.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

VoldemarG Hall of Fame Points: 3883 More actions · Answer 3

its mostly convenience.

grouping a bunch of .sql and other types of files into one comfortable bunch.

and also in the past SSMS solutions used to be integratable to TFS. no more.

its like any other project. if in 3 months i need to work on projectXXX again, but can't remember what it exactly included altogether,

i just click on SLN, and all 10 .sql files and 2 word docs and 3 screenshots and 2 txt files with notes are opened conveniently in one and the same 'location' via Solution Explorer. without further TFS integration, it is just a convenience but useful convenience. LIke Explore on top of WIndows Explorer. Something like that.

Likes to play Chess

frederico_fonseca SSCoach Points: 16154 More actions · Answer 4

moving to ssdt is not something I would advise - SSMS is a administrator tool, SSDT is a developer tool - functionality is rather different and SSDT will be missing most of the good things from SSMS.

You can always have the scripts in TSF/GIT - just not directly managed from SSMS.

but have a look at this https://cloudblogs.microsoft.com/sqlserver/2016/11/21/source-control-in-sql-server-management-studio-ssms/ as it may be an option if you manage to do the manual install.

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

Have you tried using VS Code? If you grouped your projects by folder and used VS Code's open folder function, you might get something usable.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin