Tuesday, December 06, 2011 8:11 PMLet's just suppose that I'm a user who's been using SSMS since it'sinception. Have lots of SSMS projects (suffix .ssmssln) that are series of"disembodied scripts" referring to many different databases. I want to startusing SSDT; what's the best way to convert the scripts/projects?I see that "connected mode" (AKA SSDT SQL Server Object Explorer mode) letsme open and save individual .sql files; anything better than that forconversion/SSMS compatibility purposes? I do want to have series/projects of(somehow) associated scripts at the end. And I don't want to necessarily usedisconnected and have these be converted to .sqlx.Cheers, Bob
Wednesday, December 07, 2011 7:40 AMModerator
What is the underlying goal? Create a database project? Which means changing from impartive to declarative? In that case you can create a project and using Import Script, select all the files and it will extract all the DDL statements and move the statements which are not understoood/supported in to the ScriptsIgnored.sql file. The statements/blocks most of the time end up in a post deployment script.
If you just are looking for a container for script files, you can do that, however I would argue there is no real additional value. But if you want. Create a project, add the script using Add Exitsing Item and change the Bauild Action property to be Not In Build. Now your project file is nothing more then a container for script files which does not remember connections.
-GertD @ www.sqlproj.com
Wednesday, December 07, 2011 9:10 PMHi Gert,I was thinking this would be a way to ease developers that are currently using SSMS into SSDT. Then, over time, they could take advantage of the SSDT-specific additional functionality. I’ll try your “add existing item”.Cheers, Bob
- Marked As Answer by Janet YeildingMicrosoft Employee, Owner Thursday, May 24, 2012 8:34 PM
Wednesday, December 07, 2011 10:42 PMModerator
So you just want a script container? It is very trivial create an add-in which does this either way, but I want to understand what the end-result is expected to look like.
-GertD @ www.sqlproj.com
Wednesday, February 29, 2012 5:37 AMOwner
Have your conversions been successful so far? Are you using database projects merely as "script containers" as discussed above, or are you utilizing them as declarative representation of the database?
Very interested to hear how the conversion went for you and what your current use cases in SSDT are.