SQL Data Examiner Frequently Asked Questions
- Can I setup SQL Data Examiner so it runs completely automatically?
- What versions of SQL Server does it support? Does it work with SQL Server 2008?
- Why should I use SQL Data Examiner when there is DTS, the Import/Export Wizard?
- I want to transfer data from two tables related by a foreign key into another table. However, during the synchronization process the program displays an error. How can I avoid this?
- I was transferring data to a remote server for a long time, but then a system failure occurred and the changes were rolled back. How can I avoid this problem in the future?
- I have one database and want to create a script to insert data into its tables. Is it possible?
- There are 12 columns in a table. I want to compare and update only two of them. How can I do this with SQL Data Examiner?
- Can I specify a different primary key to compare tables?
- I want to synchronize two databases; each one contains more than 100 tables, but on the second step of the comparison SQL Data Examiner displays only 90 tables. Why does this happen?
- How does SQL Data Examiner select a key column in the process of comparison, and why it is not specified for some of the tables?
Q:
Can I setup SQL Data Examiner so it runs completely automatically?
A:
Yes, SQL Data Examiner accesses command line interface and allows to automatically perform any actions available in the GUI. You may look through the “Command Line Tool” section of the Help file to learn how to specify the necessary comparison and synchronization options in the command line. To get the full list of all comparison and synchronization options, look though the “Command Line Utility Options” section. To schedule automatic comparison and synchronization of your databases, please use the built-in SQL Data Examiner Command Line Comparison and Synchronization tool and Windows Scheduled Tasks (Windows Scheduled Tasks may be found in "Control panel" » "Scheduled Tasks" of the Start menu).
Q:
What versions of SQL Server does it support? Does it work with SQL Server 2008?
A:
Yes, SQL Data Examiner 2008 works with ALL SQL Server versions from 7.0 to 2008. You can even synchronize databases that are on different versions of MS SQL Server, e.g. one on SQL Server 2005, and the other on SQL Server 2008. And of course, the tool works with all MS SQL Server editions without any restrictions.
Q:
Why should I use SQL Data Examiner when there is DTS, the Import/Export Wizard?
A:
SQL Data Examiner provides many benefits and advantages that DTS (Data Transformation Services) doesn’t offer, including:- Unlike DTS, SQL Data Examiner allows you to synchronize several columns of a table or to update only a few records;
- SQL Data Examiner compares tables and displays the differences. You can synchronize the whole database or only a few tables. You can create a back-up copy and undo any changes once the synchronization process is complete; and
- SQL Data Examiner ensures data integrity in the synchronization process.
Q:
I want to transfer data from two tables related by a foreign key into another table. However, during the synchronization process the program displays an error. How can I avoid this?
A:
In the synchronization process, there could be a temporary interruption of data integrity – for example, there could be a conflict with the foreign key. To avoid this problem, select the Disable Foreign Keys option: foreign keys are automatically disabled at the beginning of synchronization and automatically enabled when the process is finished.
Q:
I was transferring data to a remote server for a long time, but then a system failure occurred and the changes were rolled back. How can I avoid this problem in the future?
A:
On the second step of synchronization deselect the Use transaction option. Then any changes are made within an individual database transaction. Still, the referential integrity of the data can be broken if synchronization is interrupted.
Q:
I have one database and want to create a script to insert data into its tables. Is it possible?
A:
On the second step of the comparison, use the Columns drop-down list to deselect the columns you do not need compare.
Q:
There are 12 columns in a table. I want to compare and update only two of them. How can I do this with SQL Data Examiner?
A:
To write such a script you must first create the same tables in a target database (you can use SQL Examiner). Then compare the target and the source databases and save the script.
Q:
Can I specify a different primary key to compare tables?
A:
Yes, you can. SQL Data Examiner allows you to specify any key column to compare tables. The key column doesn’t even have to be a UNIQUE index or a UNIQUE constraint, but in this case the data in the columns should be unique. Also you can specify a composite key – i.e. a key composed of two or more columns. (The values of the specified columns don’t have to be unique, but the combination of the columns should be unique.) If the program finds any duplicated key values in the process of data retrieving/comparison, it interrupts the process and displays a warning.
Q:
I want to synchronize two databases; each one contains more than 100 tables, but on the second step of the comparison SQL Data Examiner displays only 90 tables. Why does this happen?
A:
On the second step of the comparison, in the Table list, the program displays only those tables that exist in both databases and have the same columns. That’s why there are usually fewer tables in the list than exist in the table.
Q:
How does SQL Data Examiner select a key column in the process of comparison, and why it is not specified for some of the tables?
A:
By default, the program uses the primary key constraint as the key column if the constraint exists in both databases. When there is no primary key, the program selects any unique index it comes across. If there are no primary keys or UNIQUE indexes, then no key column is specified.
Please also have a look at our
How To Guides
section for useful tips and articles.
