/
sec01-data-model-config.xml
1019 lines (1019 loc) · 47.2 KB
/
sec01-data-model-config.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<section version="5.0" xml:id="sec01-data-model-config" xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:svg="http://www.w3.org/2000/svg" xmlns:ns="http://docbook.org/ns/docbook"
xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:html="http://www.w3.org/1999/xhtml">
<title>Configuration Data Model</title>
<para>
The configuration is entered by the user into the data model to control the behavior of what
data is synchronized to which nodes. To ease management of several databases, nodes are put
into groups, and groups are linked together for synchronization. A trigger captures data for
a table, which can include conditions and criteria for subsets. Triggers are grouped into
channels for prioritization and control of data flow.
</para>
<para>
<figure>
<title>Configuration Data Model</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/data-model-config.gif" format="GIF" />
</imageobject>
</mediaobject>
</figure>
</para>
<section>
<title>Node Table</title>
<para>
An instance of SymmetricDS that synchronizes data with one or more nodes. Each node has
a unique identifier (nodeId) that is used when communicating, as well as a
domain-specific identifier (externalId) that provides context within the local system.
</para>
<para>
<table>
<title>node</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>Unique identifier for a node</entry>
</row>
<row>
<entry>node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>FK</entry>
<entry></entry>
<entry>The node group that this node belongs to, such as "store"</entry>
</row>
<row>
<entry>external_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
A domain-specific identifier for context within the local system.
For example, the retail store number.
</entry>
</row>
<row>
<entry>sync_enabled</entry>
<entry>booleanint</entry>
<entry>Y</entry>
<entry></entry>
<entry>0</entry>
<entry>
Indicates whether this node should be sent synchronization. Disabled
nodes are ignored by the triggers, so no entries are made in
DataEvent for the node.
</entry>
</row>
<row>
<entry>sync_url</entry>
<entry>varchar(2000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The URL to contact the node for synchronization.</entry>
</row>
<row>
<entry>schema_version</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The version of the database schema this node manages. Useful for
specifying synchronization by version.
</entry>
</row>
<row>
<entry>symmetric_version</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The version of SymmetricDS running at this node.</entry>
</row>
<row>
<entry>database_type</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The database product name at this node as reported by JDBC.
</entry>
</row>
<row>
<entry>database_version</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The database product version at this node as reported by JDBC.
</entry>
</row>
<row>
<entry>heartbeat_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The last timestamp when the node sent a heartbeat, which is
attempted every ten minutes by default.
</entry>
</row>
<row>
<entry>timezone_offset</entry>
<entry>varchar(6)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The timezone offset in RFC822 format at the time of the last heartbeat.
</entry>
</row>
<row>
<entry>created_at_node_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The id of the node where this node was created. This is filled with the
id found in node_identity where registration was opened for the node.
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Node Security Table</title>
<para>
Security features like node passwords and open registration flag are stored in the
NodeSecurity table.
</para>
<para>
<table>
<title>node_security</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>Unique identifier for a node</entry>
</row>
<row>
<entry>password</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The password used by the node to prove its identity during
synchronization.
</entry>
</row>
<row>
<entry>registration_enabled</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>0</entry>
<entry>Indicates whether registration is open for this node.</entry>
</row>
<row>
<entry>registration_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The timestamp when this node was registered.</entry>
</row>
<row>
<entry>initial_load_enabled</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>0</entry>
<entry>Indicates whether an initial load will be sent to this node.</entry>
</row>
<row>
<entry>initial_load_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The timestamp when this node started the initial load.</entry>
</row>
<row>
<entry>created_at_node_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The id of the node where this node was created. This is filled with the
id found in node_identity where registration was opened for the node.
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Node Identity Table</title>
<para>
After registration, this table will have one row representing the identity of the node.
For a root node, the row is entered by the user.
</para>
<para>
<table>
<title>node_identity</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>Unique identifier for a node</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Node Group Table</title>
<para>
A category of Nodes that synchronizes data with one or more NodeGroups. A common use of
NodeGroup is to describe a level in a hierarchy of data synchronization.
</para>
<para>
<table>
<title>node_group</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>
Unique identifier for a node group, usually named something
meaningful, like "store" or "warehouse".
</entry>
</row>
<row>
<entry>description</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>A description of this node group.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Node Group Link Table</title>
<para>
A source NodeGroup sends its data updates to a target NodeGroup using a pull, push, or
custom technique.
</para>
<para>
<table>
<title>node_group_link</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>source_node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>The node group where data changes should be captured.</entry>
</row>
<row>
<entry>target_node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>The node group where data changes will be sent.</entry>
</row>
<row>
<entry>data_event_action</entry>
<entry>char(1)</entry>
<entry>N</entry>
<entry></entry>
<entry>W</entry>
<entry>
The notification scheme used to send data changes to the target node
group. (P = Push, W = Wait for Pull)
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Channel Table</title>
<para>
A category of data that can be synchronized independently of other Channels. Channels
allow control over the type of data flowing and prevents one type of synchronization
from contending with another.
</para>
<para>
<table>
<title>channel</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>channel_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>
A unique identifer, usually named something meaningful, like "sales"
or "inventory".
</entry>
</row>
<row>
<entry>processing_order</entry>
<entry>integer</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>Order of sequence to process channel data.</entry>
</row>
<row>
<entry>max_batch_size</entry>
<entry>integer</entry>
<entry>N</entry>
<entry></entry>
<entry>1000</entry>
<entry>
The maximum number of Data Events to process within a batch for this
channel.
</entry>
</row>
<row>
<entry>max_batch_to_send</entry>
<entry>integer</entry>
<entry>N</entry>
<entry></entry>
<entry>60</entry>
<entry>
The maximum number of batches to send during a synchronization between
two nodes.
</entry>
</row>
<row>
<entry>enabled</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>Indicates whether channel is enabled or not.</entry>
</row>
<row>
<entry>description</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>Description on the type of data carried in this channel.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Node Channel Control Table</title>
<para>
The Node Channel Control is used to ignore or suspend a channel. A channel that is
ignored will have its Data Events batched and they will immediately be marked as "OK"
without sending them. A channel that is suspended is skipped when batching Data Events.
</para>
<para>
<table>
<title>node_channel_ctl</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>Unique identifier for a node</entry>
</row>
<row>
<entry>channel_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>
A unique identifer, usually named something meaningful, like "sales"
or "inventory".
</entry>
</row>
<row>
<entry>suspend_enabled</entry>
<entry>booleanint</entry>
<entry>Y</entry>
<entry></entry>
<entry>0</entry>
<entry>
Indicates if this channel is suspended, which prevents its Data
Events from being batched.
</entry>
</row>
<row>
<entry>ignore_enabled</entry>
<entry>booleanint</entry>
<entry>Y</entry>
<entry></entry>
<entry>0</entry>
<entry>
Indicates if this channel is ignored, which marks its Data Events as
if they were actually processed.
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title id="table.trigger">Trigger Table</title>
<para>
The database triggers that capture changes in the database are automatically generated
by SymmetricDS. Configuration of which triggers are generated and how they will behave
is stored in the Trigger table.
</para>
<para>
<table>
<title>trigger</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>trigger_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>Unique identifier for a trigger.</entry>
</row>
<row>
<entry>source_schema_name</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The schema name where the source table resides. The database trigger
will be created for the source_table_name in this schema.
</entry>
</row>
<row>
<entry>source_table_name</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The name of the source table that will have a trigger installed to
watch for data changes.
</entry>
</row>
<row>
<entry>target_schema_name</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The schema name where the target table resides. When data is sent
to the remote database, the SQL statements used to load the data
will qualify the target_table_name with this schema.
</entry>
</row>
<row>
<entry>target_table_name</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The name of the target table that will have data changes
synchronized to it.
</entry>
</row>
<row>
<entry>source_node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The node group that will install this trigger to watch for data
changes,
</entry>
</row>
<row>
<entry>target_node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The node group that will have data changes synchronized to it.
</entry>
</row>
<row>
<entry>channel_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>The channel that data changes will flow through.</entry>
</row>
<row>
<entry>sync_on_update</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>Whether or not to install an update trigger.</entry>
</row>
<row>
<entry>sync_on_insert</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>Whether or not to install an insert trigger.</entry>
</row>
<row>
<entry>sync_on_delete</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>Whether or not to install a delete trigger.</entry>
</row>
<row>
<entry>sync_on_incoming_batch</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>0</entry>
<entry>
Whether or not an incoming batch that loads data into this table
should cause the triggers to capture Data Events. Be careful turning
this on, because an update loop is possible.
</entry>
</row>
<row>
<entry>sync_column_level</entry>
<entry>booleanint</entry>
<entry>N</entry>
<entry></entry>
<entry>0</entry>
<entry>
Perform column level synchronization for updates, so only the
fields that changed are updated on the target database.
When updates come from multiple sources at the same time,
this enables merging of changes that do not conflict.
The entire change row is still sent, which preserves the ability
to fallback to an insert if the row does not exist.
</entry>
</row>
<row>
<entry>name_for_update_trigger</entry>
<entry>varchar(30)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Override the default generated name for the update trigger.
</entry>
</row>
<row>
<entry>name_for_insert_trigger</entry>
<entry>varchar(30)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Override the default generated name for the insert trigger.
</entry>
</row>
<row>
<entry>name_for_delete_trigger</entry>
<entry>varchar(30)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Override the default generated name for the delete trigger.
</entry>
</row>
<row>
<entry>sync_on_update_condition</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a condition for the update trigger firing using an
expression specific to the database.
</entry>
</row>
<row>
<entry>sync_on_insert_condition</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a condition for the insert trigger firing using an
expression specific to the database.
</entry>
</row>
<row>
<entry>sync_on_delete_condition</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a condition for the delete trigger firing using an
expression specific to the database.
</entry>
</row>
<row>
<entry>initial_load_select</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a where-clause for an initial load of this table. The table
is aliased as "t". Replacement variables are $(nodeId),
$(groupId), and $(externalId).
</entry>
</row>
<row>
<entry>node_select</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a where-clause for selecting the nodes that will receive
data changes. The node table is aliased as "c".
</entry>
</row>
<row>
<entry>tx_id_expression</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Override the default expression for the transaction identifier that
groups the data changes that were committed together.
</entry>
</row>
<row>
<entry>excluded_column_names</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Specify a comma-delimited list of columns that should not be
synchronized from this table.
</entry>
</row>
<row>
<entry>initial_load_order</entry>
<entry>integer</entry>
<entry>N</entry>
<entry></entry>
<entry>1</entry>
<entry>
Order sequence of this table when an initial load is sent to a node.
</entry>
</row>
<row>
<entry>create_time</entry>
<entry>timestamp</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>Timestamp when this entry was created.</entry>
</row>
<row>
<entry>inactive_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
Timestamp when this entry was inactivated, which stops capturing of
data changes.
</entry>
</row>
<row>
<entry>last_updated_by</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The user who last updated this entry.</entry>
</row>
<row>
<entry>last_updated_time</entry>
<entry>timestamp</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>Timestamp when a user last updated this entry.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Parameter Table</title>
<para>
The Parameter table provides a way to manage most SymmetricDS settings in the database.
</para>
<para>
<table>
<title>parameter</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>external_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>Target the parameter at a specific external id. To target all nodes, use the value of 'ALL.'</entry>
</row>
<row>
<entry>node_group_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>
Target the parameter at a specific node group id. To target all groups, use the value of 'ALL.'
</entry>
</row>
<row>
<entry>param_key</entry>
<entry>varchar(100)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>
The name of the parameter.
</entry>
</row>
<row>
<entry>param_value</entry>
<entry>varchar(1000)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The value of the parameter.
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section>
<title>Registration Redirect Table</title>
<para>
The Registration redirect table provides a way for a centralized registration server to redirect registering Nodes to their prospective
parent Node in a multi-tiered deployment.
</para>
<para>
<table>
<title>registration_redirect</title>
<tgroup cols="6">
<colspec colwidth="115px" />
<colspec colwidth="65px" />
<colspec colwidth="25px" />
<colspec colwidth="25px" />
<colspec colwidth="40px" />
<colspec colwidth="250px" />
<thead>
<row>
<entry>Column Name</entry>
<entry>Type</entry>
<entry>Null</entry>
<entry>Key</entry>
<entry>Default</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>registrant_external_id</entry>
<entry>varchar(50)</entry>