Now, the same process from the step 3) to step 7) needs to be repeated for the Target side in order to set everything to compare two SQL databases The OK button should be clicked in order to load the source data source:
Once all information is loaded, the Select Source Schema dialog will be shown again and here Network or Azure list of sources that might already exist, or byĭirectly providing Server Name, Authentication type, andĪfter all information for SQL Server and database are entered, click the Connect button: History – in which all previous connections can be seen and selected:īrowse – in which a new connection can be set via Local, This will bring the new Connect dialog in which there are two tabs: The Select Source Schema dialog will be shown and in it, by default, theĭatabase option is selected and under it, click the Select Connection button: Note: If there were some previous SQL Server database schema comparisons, data sources will be shown in this Select source drop-down list and click on the Select Source In the upper left corner of the SqlSchemaCompare query window, locate the To select source and target from their corresponding drop-down lists:
This will load the SqlSchemaCompare query window and the first thing that needs to be done is To compare two SQL databases with Visual Studio’s Schema Compare feature, follow these steps:įrom the main menu, go to the Tools -> SQL Server sub-menu -> On which additional testing should be done before moving to production. This is a neat feature, as it facilitates work for developers who are working on database development and need a quick way to synchronize the latest changes with the QA database, Among these features, Visual Studio offers users the feature to compare two SQLĭatabases via its Schema compare feature.īesides comparing SQL Server database locally or on the network, Visual Studio can connect and compare Azure SQLĭatabase as well. Visual Studio is an application that is used by many developers and it has different kinds of features that can facilitate the developer’s work.
0 kommentar(er)
