Skip to content
Azure Data Studio Extension: Scripts table data
TypeScript JavaScript
Branch: master
Clone or download
Sean Price
Sean Price Updated readme
Latest commit 72b8cfd Nov 11, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Initial Commit Sep 17, 2019
.vscodeignore Initial Commit Sep 17, 2019
LICENSE Added License File Sep 19, 2019 Updated readme Nov 11, 2019
installTypings.js Initial Commit Sep 17, 2019
package-lock.json Initial Commit Sep 17, 2019
package.json Updated package.json to show context menu on Views node to enable scr… Nov 11, 2019
tsconfig.json Initial Commit Sep 17, 2019
tslint.json Initial Commit Sep 17, 2019

FeatureAzure Data Studio - Simple Data Scripter

This extension provides a quick and easy way to migrate data between tables by generating insert scripts based on the result sets of a query. It defaults to generating all data from a given table (based on the table selected via a context menu), but the default sql can be modifed to generate subsets of data.


The current release is available to download as a .vsix file and can be installed by opening the File Menu and selecting Install Extension from VSIX Package


Right-click on a Table or View node to bring up a [Script Table Data] context menu. An input box will open showing the default SQL of selecting all data. You can simply press [Enter] to accept the default or the SQL using a WHERE clause, joins on other tables, etc... Any valid SQL is acceptable. Press [Enter] to run the query. The data will be scripted to a new SQL Editor window. Feature

Known Issues

  • This has only been tested with the MSSQL provider, i.e. Microsoft SQL Server. If there are any issues found with other flavors of SQL, (MySql, etc..) please report them at
  • Scripting of binary data (binary, varbinary, image) is not currently supported.

Unknown Issues

Can be raised here:

Release Notes


  • Show context menu on View nodes to enable scripting of View data as well as Table data


  • Ensure data retrieval query is run in proper database context


  • Initial release.
You can’t perform that action at this time.