Files
azuredatastudio/extensions/schema-compare
Charles Gagnon 3cb2f552a6 Merge from vscode a348d103d1256a06a2c9b3f9b406298a9fef6898 (#15681)
* Merge from vscode a348d103d1256a06a2c9b3f9b406298a9fef6898

* Fixes and cleanup

* Distro

* Fix hygiene yarn

* delete no yarn lock changes file

* Fix hygiene

* Fix layer check

* Fix CI

* Skip lib checks

* Remove tests deleted in vs code

* Fix tests

* Distro

* Fix tests and add removed extension point

* Skip failing notebook tests for now

* Disable broken tests and cleanup build folder

* Update yarn.lock and fix smoke tests

* Bump sqlite

* fix contributed actions and file spacing

* Fix user data path

* Update yarn.locks

Co-authored-by: ADS Merger <karlb@microsoft.com>
2021-06-17 08:17:11 -07:00
..
2020-03-11 19:25:32 -07:00
2021-06-15 11:51:35 -07:00

Microsoft SQL Server Schema Compare for Azure Data Studio

Microsoft SQL Server Schema Compare for Azure Data Studio includes:

Schema Compare

The Schema Compare extension provides an easy to use experience to compare .dacpac files and databases and apply the changes from source to target.

Please report issues and feature requests here.

schemacompare0506

How do I start a Schema Comparison?

  • The main entry point for schema compare is to right click a database in the Object Explorer, and click Schema Compare.
  • The user can also launch the schema compare dialog from the command palette (Ctrl+Shift+P) by searching for Schema Compare

Why would I use the Schema Compare?

Schema Compare was created to add the ability to compare the schemas from .dacpac files and databases and apply the changes.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Privacy Statement

The Microsoft Enterprise and Developer Privacy Statement describes the privacy statement of this software.

License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the Source EULA.