|
|
 |
| Product
Information | Product Tour | Pricing | Testimonials |
| Product
Tour |
| Compare
and Synchronize Microsoft SQL Server Databases (Step 1) (2)
(3) (4) (5) |
|
1.
Connecting to the databases -
you select the source and target Microsoft SQL Server database
|
|
|
|
The
first step in the database synchronization is connecting to the
SQL Server databases. When you run the DB SynchroComp, a connection
dialog box will open, offering you to connect to the source and
target databases. You can do this later, if you select Connect option
from the menu. The source database is the database that is read-only
in this case i.e. the one that has a preferred structure. The target
database is the one that should be synchronized with the source
database. You can connect to any MS SQL Server available on your
network. From the list of available databases on the chosen server
choose the SQL Server name first and than the database name. You
have the ability to logically organize the servers into a tree list
and thus easily manage your connections. DB SynchroComp will remember
all your previous connections, so if you want, you can choose to
do the comparison based on the parameters from the previous one.
You must have the access rights for all the relevant database objects
in both databases. If you don't have the right to create an object
in the target database, you will not be able to select it in the
list of database objects that are to be synchronized, nor will the
script be created for that object.
|
| (Step
2) Top |
|
2.
Comparing the databases
- DB SynchroComp compares the SQL Server databases and determines
what actions are necessary to be taken in order to synchronize the
databases
|
|
|
|
After you connect to the SQL Servers, DB SynchroComp will compare
the two databases and show all the differences. By default, the
main program window is divided into three parts. The first one,
called the "Differences view", shows objects that are
different in two databases.
The database objects are graphically displayed in a hierarchical
structure. Only those objects that differ in a way are shown. If
the two objects exist in both databases, but are different, then
the row in which they appear is colored in blue. If an object exists
only in one database, the row in which it appears is colored in
red and the object is displayed only in the database where it exists.
Two other parts of the main program window are used to show the
SQL script for object creation in the source and target database.
|
| (Step
3) Top |
|
3.
Setting comparison options
- you determine the rules by which the DB SynchroComp will behave
when comparing the databases
|
|
|
|
If you wish, you can change the comparison options, and repeat the
comparison. Repeated comparison will be done using cached data,
and thus it will be much faster. If you are satisfied with the comparison
results, you can generate the synchronization script.
|
| (Step
4) Top |
|
4.
Creating the synchronization script
- you select the objects that are to be synchronized and order the
DB SynchroComp to create a SQL script that will annul the differences
|
|
|
|
The script could either be made only for selected objects or for
the entire database.
The synchronization script will be displayed in the editor, which
has a syntax highlighting that is exactly the same as Microsoft
Query Analyzer. There is no syntax checking before the script execution.
If
you want, you can edit the synchronization script before running
it. There is a certain risk when using this option, so it is up
to you to decide whether to use it or not. Hence, although it is
possible to type everything you imagine into the script, its changing
is not recommended unless you are sure that you completely understood
it. After the generation of the synchronization script, it can be
executed. It will be executed in transaction, so if something goes
wrong, your database will be restored to its previous state.
|
| (Step
5) Top |
|
5.
Running the synchronization script
- execute a SQL script and you are done with it
|
|
|
|
The
script could either be made only for selected objects or for the
entire database.
The synchronization script will be displayed in the editor, which
has a syntax highlighting that is exactly the same as Microsoft
Query Analyzer. There is no syntax checking before the script execution.
Hence, although it is possible to type everything you imagine into
the script, its changing is not recommended unless you are sure
that you completely understood it. After the generation of the synchronization
script, it can be executed. It will be executed in transaction,
so if something goes wrong, your database will be restored to its
previous state.
|
| Product
Information | Product Tour | Pricing | Testimonials |
Top |