You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: connectors/mssql/README.md
+40-70Lines changed: 40 additions & 70 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# redis-connect-sqlserver
2
2
3
-
redis-connect-sqlserver is a Redis Connect connector for capturing changes (INSERT, UPDATE and DELETE) from MS SQL Server (source) and writing them to a Redis Enterprise database (Target).
3
+
redis-connect-sqlserver is a Redis Connect connector for capturing changes (INSERT, UPDATE and DELETE) from MS SQL Server (source) and writing them to a Redis Enterprise database (Target). redis-connect-sqlserver implementation is based on [Debezium](https://debezium.io/documentation/reference/stable/connectors/sqlserver.html), which is an open source distributed platform for change data capture.
4
4
5
5
<p>
6
6
The first time redis-connect-sqlserver connects to a SQL Server database/cluster, it reads a consistent snapshot of all of the schemas.
@@ -101,7 +101,7 @@ Copy the _sample_ directory and it's contents i.e. _yml_ files, _mappers_ and te
101
101
### Sample logback.xml under redis-connect-sqlserver/config folder
redisUrl: redis://127.0.0.1:14001 #Metrics Redis database, can be same as Job Configuration database.
214
-
msSQLServerConnection:
215
-
database:
216
-
name: testdb #database name same as database value in Setup.yml
217
-
db: RedisConnect #database
218
-
hostname: 127.0.0.1
219
-
port: 1433
220
-
username: sa #This can be a non privileged user. Please see an example in the demo, https://github.com/RedisLabs-Field-Engineering/redis-connect-dist/blob/main/connectors/mssql/demo/mssql_cdc.sql#L36
221
-
password: Redis@123
222
-
type: mssqlserver #this value cannot be changed for mssqlserver
### Sample JobManager.yml under redis-connect-sqlserver/config/samples/sqlserver folder
294
286
295
287
```yml
296
-
connectionId: jobConfigConnection # This refers to connectionId from env.yml for Job Config Redis
297
-
jobTypeId: jobType1 #Variable
298
-
jobStream: jobStream
299
-
jobConfigSet: jobConfigs
300
-
initialDelay: 10000
301
-
numManagementThreads: 2
288
+
connectionId: jobConfigConnection
302
289
metricsReporter:
303
290
- REDIS_TS_METRICS_REPORTER
304
-
heartBeatConfig:
305
-
key: hb-jobManager
306
-
expiry: 30000
307
-
jobHeartBeatKeyPrefix: "hb-job:"
308
-
jobHeartbeatCheckInterval: 45000
309
-
jobClaimerConfig:
310
-
initialDelay: 10000
311
-
claimInterval: 30000
312
-
heartBeatConfig:
313
-
key: "hb-job:"
314
-
expiry: 30000
315
-
maxNumberOfJobs: 2#This indicates the maximum number of Jobs a single RedisConnect instance can execute
316
-
consumerGroup: jobGroup
317
-
batchSize: 1
318
291
```
319
292
320
293
</p>
@@ -330,34 +303,31 @@ jobClaimerConfig:
330
303
You can have one or more JobConfig.yml (or with any name e.g. JobConfig-<table_name>.yml) and specify them in the Setup.yml under jobConfig: tag. If specifying more than one table (as below) then make sure maxNumberOfJobs: tag under JobManager.yml is set accordingly e.g. if maxNumberOfJobs: tag is set to 2 then Redis Connect will start 2 cdc jobs under the same JVM instance. If the workload is more and you want to spread out (scale) the cdc jobs then create multiple JobConfig's and specify them in the Setup.yml under jobConfig: tag.
331
304
332
305
```yml
333
-
jobId: ${jobId}#Unique Job Identifier. This value is the job name from Setup.yml
306
+
jobId: ${jobId}
334
307
producerConfig:
335
308
producerId: RDB_EVENT_PRODUCER
336
-
connectionId: testdb-msSQLServerConnection #Name of the Redis connection id specified in env.yml
309
+
connectionId: RDBConnection
337
310
tables:
338
-
- dbo.emp #Name of the table with SCHEMA.TABLE format
339
-
# - dbo.dept #Name of the table with SCHEMA.TABLE format
0 commit comments