Azuredatastudio: Seeking community feedback on SQL Database Projects extension (Insiders preview)

[dzsquared]

To bring project-based SQL database development to a cross-platform experience, we are announcing SQL Database Projects Extension (Insiders Preview) is now available in the latest Azure Data Studio Insiders build.

Getting Started with SQL Database Projects

• Create a new database project by going to the Projects viewlet under Explorer, or by searching for New Database Project in the command palette.
• Existing database projects can be opened via Open Database Project in the command palette.
• Start from an existing database by using Import New Database Project from the command palette.

Official documentation is available here.

Get started with database projects in Azure Data Studio today by grabbing the latest Azure Data Studio Insiders build.

[ErikEJ]

The linked "data tier application" article has too much confusing emphasis on .bacpac (and not enough on .dacpac)

[rrmistry]

Firstly, great work team 👍 Huge thanks from our whole team ❤️ !!!

Our specific requests by priority:

1. Ability to select verbosity of output for any SSDT tasks
   (e.g. "Import Project from Database" only creates 1 line log for import task saying "Extract project files succeeded ...")
2. Closer integration between Azure Data Studio folder workspaces and active SSDT project
   
   
   
   1. Is it possible to have a default *.sqlproj file that is always opened in a workspace? Something we can specify in the workspace settings?
      
      (ideally something that can be parameterized like "${workspaceFolder}/${workspaceFolderBasename}.sqlproj")
   
   
   2. We have 1500+ objects in our SSDT project. This is tedious to navigate when the project is first opened. Could we have a "collapse folders" button on the Projects panel? (similar to "Collapse Folders in Explorer" button on folder panel)
   
   
   3. For newly imported project from database, open the project folder as workspace when import starts
   
   
   4. Prompt to initialize Git repo with default .gitignore and .gitattributes generated for SSDT project (similar to VS Git initialization)
   
   
3. Ability to chain together build and deploy activities automatically from tasks. Maybe with https://github.com/microsoft/azuredatastudio/issues/10370
4. SQL synonym support for multi-schema databases
   Workaround available: manually edit *.sqlproj XML and add synonym that way
5. Simple support for pre/post deployment scripts. Maybe just allow users to use UI to add / remove these script
   Workaround available: manually edit *.sqlproj XML and add pre/post deployment scripts that way
6. Self-contained SSDT support without requiring users to install .NET Core SDK
   Acknowledge this is a big ask so low priority but very nice to have