/
sec02-data-model-runtime.xml
878 lines (878 loc) · 41.2 KB
/
sec02-data-model-runtime.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
<?xml version="1.0" encoding="UTF-8"?>
<section version="5.0" xml:id="ch03-data-model-runtime" 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>Runtime Data Model</title>
<para>
At runtime, the configuration is used to capture data changes and route them to nodes. The
data changes are placed together in a single unit called a batch that can be loaded by
another node. Outgoing batches are delivered to nodes and acknowledged. Incoming batches are
received and loaded. History is recorded for batch status changes and statistics.
</para>
<para>
<figure>
<title>Runtime Data Model</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/data-model-runtime.gif" format="GIF" />
</imageobject>
</mediaobject>
</figure>
</para>
<section id="ch03-trigger-history">
<title>Trigger History Table</title>
<para>
A history of a table's definition and the Trigger used to capture data from the table.
When a database trigger captures a data change, it references a Trigger Hist entry
so it is possible to know which columns the data represents.
Trigger Hist entries are made during the sync trigger process, which runs at
each startup, each night in the SyncTriggersJob, or any time the syncTriggers() JMX
method is manually invoked.
A new entry is made when a table definition or a Trigger definition is changed, which
causes a database trigger to be created or rebuilt.
</para>
<para>
<table>
<title>trigger_hist</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_hist_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>Unique identifier for a Trigger Hist.</entry>
</row>
<row>
<entry>trigger_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>FK</entry>
<entry></entry>
<entry>Unique identifier for a Trigger.</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>source_catalog_name</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The catalog name where the source table resides.</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.</entry>
</row>
<row>
<entry>name_for_insert_trigger</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>The name used when the insert trigger was created.</entry>
</row>
<row>
<entry>name_for_update_trigger</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>The name used when the update trigger was created.</entry>
</row>
<row>
<entry>name_for_delete_trigger</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>The name used when the delete trigger was created.</entry>
</row>
<row>
<entry>table_hash</entry>
<entry>integer</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>A hash of the table definition, used to detect changes
in the definition.</entry>
</row>
<row>
<entry>column_names</entry>
<entry>longvarchar</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The column names defined on the table.
The column names are stored in comma-separated values (CSV) format.
</entry>
</row>
<row>
<entry>pk_column_names</entry>
<entry>longvarchar</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The primary key column names defined on the table.
The column names are stored in comma-separated values (CSV) format.
</entry>
</row>
<row>
<entry>last_trigger_build_reason</entry>
<entry>char(1)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The following reasons for a change are possible:
New trigger that has not been created before (N);
Schema changes in the table were detected (S);
Configuration changes in Trigger (C);
Trigger was missing (T).
</entry>
</row>
<row>
<entry>create_time</entry>
<entry>timestamp</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when this entry was recorded.</entry>
</row>
<row>
<entry>inactive_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when a Trigger was inactivated.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-data">
<title>Data Table</title>
<para>
The captured data change that occurred to a row in the database.
Entries in Data are created by database triggers.
</para>
<para>
<table>
<title>data</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>data_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>Unique identifier for a data</entry>
</row>
<row>
<entry>table_name</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry></entry>
<entry></entry>
<entry>
The name of the table in which a change occurred that this entry
records.
</entry>
</row>
<row>
<entry>event_type</entry>
<entry>char(1)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The type of event captured by this entry. For triggers, this is the
change that occurred, which is "I" for insert, "U" for update, or
"D" for delete. Other events include: "R" for reloading the entire
table (or subset of the table) to the node; "S" for running dynamic
SQL at the node, which is used for adhoc administration.
</entry>
</row>
<row>
<entry>row_data</entry>
<entry>longvarchar</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The captured data change from the synchronized table. The column
values are stored in comma-separated values (CSV) format.
</entry>
</row>
<row>
<entry>pk_data</entry>
<entry>longvarchar</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The primary key values of the captured data change from the
synchronized table. This data is captured for updates and deletes.
The primary key values are stored in comma-separated values (CSV)
format.
</entry>
</row>
<row>
<entry>trigger_hist_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>FK</entry>
<entry></entry>
<entry>
The foreign key to the Trigger Hist entry that contains the primary
key and column names for the table being synchronized.
</entry>
</row>
<row>
<entry>create_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The timestamp when the data change was captured.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-data-event">
<title>Data Event Table</title>
<para>
The Data Event represents routing of a Data to one or more Nodes.
Entries in Data Event are created by database triggers.
</para>
<para>
<table>
<title>data_event</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>data_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>The Data that will be routed.</entry>
</row>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK FK</entry>
<entry></entry>
<entry>The Node that will receive the Data.</entry>
</row>
<row>
<entry>channel_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>FK</entry>
<entry></entry>
<entry>The channel that this data belongs to, such as "prices"</entry>
</row>
<row>
<entry>transaction_id</entry>
<entry>varchar(1000)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
An optional transaction identifier that links multiple data changes
together as the same transaction.
</entry>
</row>
<row>
<entry>batch_id</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry>FK</entry>
<entry></entry>
<entry>
A unique identifier for a batch that will be a unit of
delivery for multiple Data Events.
</entry>
</row>
<row>
<entry>batched</entry>
<entry>char(1)</entry>
<entry>N</entry>
<entry></entry>
<entry>0</entry>
<entry>
Whether or not this Data Event is prepared for a batch.
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-outgoing-batch">
<title>Outgoing Batch Table</title>
<para>
The Outgoing Batch is used for tracking the sending a collection
of Data to a Node in the system. A new Outgoing Batch is created by the
Outgoing Batch Service and given a status of "NE". After sending the Outgoing Batch
to its target Node, the status becomes "SE". The Node responds with either a success
status of "OK" or an error status of "ER". An error while sending to the Node
also results in an error status of "ER" regardless of whether the Node sends that
acknowledgement.
</para>
<para>
<table>
<title>outgoing_batch</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>batch_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>A unique ID for the Batch.</entry>
</row>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The Node that will be sent this Batch.</entry>
</row>
<row>
<entry>channel_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The Channel that categorizes the Data in this Batch.</entry>
</row>
<row>
<entry>batch_type</entry>
<entry>char(2)</entry>
<entry>N</entry>
<entry></entry>
<entry>EV</entry>
<entry>
Batch types include events from triggers when rows change (EV)
and initial loads of data that send an entire table (IL).
</entry>
</row>
<row>
<entry>status</entry>
<entry>char(2)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The current status of the Batch can be newly created (NE),
sent to a Node (SE), acknowledged as successful (OK),
and error (ER).
</entry>
</row>
<row>
<entry>create_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the Batch was created.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-outgoing-batch-history">
<title>Outgoing Batch History Table</title>
<para>
A history of status changes to the Outgoing Batch, along with statistics of
the work performed.
</para>
<para>
<table>
<title>outgoing_batch_hist</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>batch_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>A unique ID for the Batch.</entry>
</row>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The Node that will be sent this Batch.</entry>
</row>
<row>
<entry>status</entry>
<entry>char(2)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The current status of the Batch can be newly created (NE),
sent to a Node (SE), acknowledged as successful (OK),
or error (ER).
</entry>
</row>
<row>
<entry>start_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the process for this entry was started. (1.4)</entry>
</row>
<row>
<entry>end_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the process for this entry was ended. (1.4)</entry>
</row>
<row>
<entry>data_event_count</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The number of Data Events in the Batch. This is only populated
for a new status (NE).
</entry>
</row>
<row>
<entry>failed_data_id</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the Data entry that was being processed
when the Batch failed.</entry>
</row>
<row>
<entry>hostname</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The name of the machine processing the Batch, which is meaningful
when running a cluster of SymmetricDS instances. (1.4)
</entry>
</row>
<row>
<entry>network_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent using the network to send the Batch.
This is currently unimplemented. (1.4)
</entry>
</row>
<row>
<entry>filter_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent in filters.
This is currently unimplemented. (1.4)
</entry>
</row>
<row>
<entry>database_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent in the database.
This is only populated for a status of new (NE). (1.4)
</entry>
</row>
<row>
<entry>sql_state</entry>
<entry>varchar(10)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the XOPEN or SQL 99 SQL State. (1.4)
</entry>
</row>
<row>
<entry>sql_code</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the error code
from the database that is specific to the vendor. (1.4)
</entry>
</row>
<row>
<entry>sql_message</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the error message
that describes the error. (1.4)
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-incoming-batch">
<title>Incoming Batch Table</title>
<para>
The Incoming Batch is used for tracking the status of loading an Outgoing Batch
from another Node. Data is loaded and commited at the batch level.
The status of the Incoming Batch is either successful (OK) or error (ER).
</para>
<para>
<table>
<title>incoming_batch</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>batch_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>A unique ID for the Batch.</entry>
</row>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>The Node that sent this Batch.</entry>
</row>
<row>
<entry>status</entry>
<entry>char(2)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The current status of the Batch can be successfully
loaded (OK) or error (ER).
</entry>
</row>
<row>
<entry>create_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the Batch was first received.</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
<section id="ch03-incoming-batch-history">
<title>Incoming Batch History Table</title>
<para>
A history of status changes to the Incoming Batch, along with statistics of
the work performed.
</para>
<para>
<table>
<title>incoming_batch_hist</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>batch_id</entry>
<entry>integer</entry>
<entry>N</entry>
<entry>PK</entry>
<entry></entry>
<entry>A unique ID for the Batch.</entry>
</row>
<row>
<entry>node_id</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The Node that sent this Batch to be loaded.</entry>
</row>
<row>
<entry>status</entry>
<entry>char(2)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The current status of the Batch can be loaded successfully (OK),
skipped because previously loaded (SK), or error (ER).
</entry>
</row>
<row>
<entry>start_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the load for this entry was started.</entry>
</row>
<row>
<entry>end_time</entry>
<entry>timestamp</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>The date and time when the load for this entry was ended.</entry>
</row>
<row>
<entry>failed_row_number</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the row number (starting with row one)
that was being processed when the Batch failed.</entry>
</row>
<row>
<entry>hostname</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The name of the machine processing the Batch, which is meaningful
when running a cluster of SymmetricDS instances.
</entry>
</row>
<row>
<entry>network_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent using the network to receive the Batch.
This is currently unimplemented.
</entry>
</row>
<row>
<entry>filter_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent in filters.
This currently includes time from IDataLoaderFilters.
</entry>
</row>
<row>
<entry>database_millis</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
The amount of time in milliseconds spent in the database.
</entry>
</row>
<row>
<entry>sql_state</entry>
<entry>varchar(10)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the XOPEN or SQL 99 SQL State. (1.4)
</entry>
</row>
<row>
<entry>sql_code</entry>
<entry>integer</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the error code
from the database that is specific to the vendor. (1.4)
</entry>
</row>
<row>
<entry>sql_message</entry>
<entry>varchar(50)</entry>
<entry>Y</entry>
<entry></entry>
<entry></entry>
<entry>
For a status of error (ER), this is the error message
that describes the error. (1.4)
</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
</section>
</section>