search

microsoft / azuredatastudio

Azure Data Studio is a data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server. Browse the extension library for more database support options including MySQL, PostgreSQL, and MongoDB.
https://learn.microsoft.com/sql/azure-data-studio
MIT License
7.58k stars 908 forks source link

Script CREATE DATABASE #390

Open joshbooker opened 6 years ago

joshbooker commented 6 years ago

Would be nice to right click on database and generate CREATE DATABASE script.

kevinvngo commented 6 years ago

It would be great if this applies to SQL DW/DB as well. Similar to the SSMS create database wizard experience where the user can select different databases and and their configurations. image

yualan commented 3 years ago

This request also came from the most recent Azure Data Studio UX Benchmark. We do have an extension that @kevcunnane created, potentially something we include as default?

spencer741 commented 3 years ago

First off, thank you @yualan for adding the appropriate Impact -UX Research label, because it 100% applies.

Now... Looks like similar functionality illustrated in Issue #7455 was added to the backlog, with the "Script as Create" being added to the context menu of database object nodes.

"Script as Create" context menu addition and a "Generate Scripts" Wizard would be nice to include as default as you mention. [view edit at the bottom for more]

Now, abstracting a bit more... the "Database Administration Tool Extensions for Windows" adds the "Generate Scripts" dialog, but for windows only as I discovered per this discussion. This functionality would be nice to have as default, pending a more complete picture to what Azure Data Studio's purpose is.

I myself was about to embark on creating an extension that re-created SSMS's "Generate Scripts" wizard so cross-platform usage could be obtained (since the extension that adds that is windows only)... but I am questioning if I should after more research.

If looking at ADS as a noteworthy successor to SSMS (plus a lot more), where is the line drawn between default Wizards/Context menus like the above versus relying on someone to develop a 3rd party extension?

On a side note: It seems as if development of default VSCode functionality can heavily rely 3rd party extensions as it is (and rightly so), but ADS will have to push that boundary of including a lot more default features to get more people to migrate from SSMS if that is the ultimate goal.

Tagging @kevcunnane and @Charles-Gagnon .

EDIT: As I ponder this, in SSMS, "Script Table as" context menu with sub menu's illustrating "[CRUD operation] to" -> "New Query Editor Window", "File", "Clipboard" is extremely useful shorthand for what "Generate Scripts" also does) ... Perhaps all issues (rather feature requests) relating to auto-generated scripts should be funneled into one issue (something I could certainly help out with) and possibly tethered to a GH project as well ... this might help track what is a more of a global task here and help drive whatever business decisions are associated with the whole "What ADS features should be native vs left up to extension community" that I outlined above (which should also be analyzed from a ADS vs SSMS perspective as well for coverage).