With Schema Compare, you can compare and synchronize Microsoft Azure SQL databases.
|Application Roles||Partition Schemes|
|Asymmetric Keys||Remote Synonyms|
|Event Notifications||Service Bindings|
|Extended Stored Procedures||Symmetric Keys|
|Full Text Catalogs||System Tables|
|Message Types||User-Defined Types|
|Numbered Stored Procedures||XML Schema Collections|
If you try to synchronize unsupported objects to a Microsoft Azure SQL database, the synchronization script will fail.
Relational index options that are not supported:
Synonyms cannot be created for objects on different server; i.e. Azure supports the three-part name format [database_name].[schema_name].[object_name] when the database_name is the current database or the database_name is tempdb and the object_name starts with #. It means that Azure does not support synonyms, that reference objects using four-part names in form: [server_name].[database_name].[schema_name].[object_name].
Azure does not support the following options for tables:
Azure does not support users based on Windows Logins;
User can be created only for some specific login, while logins can be created only in a master database. So user creation logic is as follows: create a login in a master database (if not exist yet) and then create a user in a custom database for this login;
Microsoft Azure SQL databases have some other limitations that can lead to Schema Compare synchronization failure. For instance, Microsoft Azure SQL databases don’t support encryption, data compression, and SQL Server replication.