-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathconfig.properties.example
69 lines (60 loc) · 2.23 KB
/
config.properties.example
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
# target MonetDB Database:
monetdb.user = monetdb
monetdb.password = ENV:MONETDB_PASSWORD:monetdb
monetdb.server = localhost
monetdb.database = my_monetdb
# source MS SQL Server database(s):
# multiple databases can be specified, each under their own sub-key
mssql.db1.user = dbuser
mssql.db1.password = dbpassword
mssql.db1.server = localhost
mssql.db1.database = my_db
# optional instance name
# mssql.db1.instance = instance_name
# copy a table
table.example.source = db1
table.example.from = example_table
table.example.to = example_table_new
table.example.schema = sys
table.example.create = true
table.example.truncate = true
# use tmp_tables to copy the data to so we can recreate the
# to-table for faster data transfer to the end table which
# reduces down-time
table.example.copyViaTempTable = true
table.example.tempTablePrefix = tmp_
# this will create views with the table.example.to name
# and will backup your table to a backup table
# this will make it possible to switch the underlying table
# of the view when data copying is complete
# resulting in almost no down-time of your database table
# prefixes can be defined if you want custom naming
table.example.useFastViewSwitching = false
# Mail settings
monetdb.mail.sendmail=true
monetdb.mail.server=1.1.1.1
monetdb.mail.port=8888
monetdb.mail.username=
monetdb.mail.password=
# specifies a custom temp directory instead of the default system temp directory
# temp.directory = /home/me/temp
# indicates how many records should be insert at a time into MonetDB
# only used when using INSERT method to insert new data.
batch.size = 10000
# Scheduling options
# Enabling the scheduler will run the tool indefinitely and run the copy job
# every X minutes/hours/days. Very useful in combination with the trigger options
#
# scheduler.enabled = true
# scheduler.interval = every 5 minutes
# Trigger options
# With this the tool will check this table/column in SQL server and determine
# if there have been any changes since the last run. The copy job will only be executed
# if there is new data in the trigger column.
#
# trigger.enabled = true
# trigger.source = db1
# trigger.table = updated
# trigger.column = last_updatetime