Skip to main content
Skip table of contents

DigErase-DigAlign-WebAlign: Manual copy process for table alignment for DigAlign

Q: We want to use DigAlign to align our music table between two cities. One city is the master and city B is the slave. We used unique MusicIDs for use in the music planning tool in city A. Because of the low bandwidth of our WAN connection we don't want to make an initial alignment of our existing music content because we have too much content inside this table in city A. What can we do?

A: There is a special option within DigAlign to create its brain file (*.RNM). This file is used to synchronize the entries in table A and table B.

Normally the RNM file is created by DigAlign by starting the initial alignment process. In your case you want to copy the content e.g. on a removable disk and import all files manually at your city B. Here are the instructions what to do:

1. Configure your DigAlign table alignment, but don't start the alignment.
2. Copy all elements to your removable disk.
3. Import the files from the removable disk to the empty table of the database server in city B.
4. Open the DigAlign table alignment profile, go to settings --> table alignment.
5. In the table alignment settings window select the corresponding table pair in the white part of the window.
6. Press the 'Special' button.
7. Select the option 'Create new RNM file'.
8. Confirm the security warning.
9. Enter the field name which contains unique IDs or content for table A and B, e.g. MUSICID or TITLE.
10. Press OK to start the alignment.
11. Press OK.
12. Press OK to close the alignment window.
13. Press the 'Back' button.
14. Enable the 'Test run only' button.
15. Close the window by pressing OK.
16. Try to start an alignment process. No action should happen because the content of both tables should be the same.
17. Create a new element.
18. Test DigAlign alignment process once again.

That's it. Now you can remove the 'Test run only' button.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.