From 913cd879b73282446c7f90f82fac3b064c3ec3dd Mon Sep 17 00:00:00 2001 From: Ilian Iliev Date: Mon, 14 Sep 2026 14:25:20 +0300 Subject: [PATCH 1/3] Improving SQL Server setup documentation when using custom types --- .../data-pipelines/prepare-dbs/sql-server.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md index 19f91ca52f..445d780aa8 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md @@ -205,6 +205,21 @@ EXEC xp_servicecontrol N'START',N'SQLServerAGENT'; GO ``` +## 5. Using SQL Server with custom data fields + +When using custom data types, you need to ensure that the Debezium user has the necessary permissions to access +those types. You can grant these permissions using the following SQL commands: + +```sql +USE ; + +GRANT REFERENCES ON TYPE::. TO ; +``` + +Without granting these permissions you may encounter errors like: +`"The column "Account" is referenced as PRIMARY KEY, but a matching column is not defined in table "DB.dbo.MyTable"!"` + + ## SQL Server capture job agent configuration parameters In SQL Server, the parameters that control the behavior of the capture job agent @@ -781,4 +796,4 @@ documentation for further details. {{< note >}}RDI will *not* correctly capture changes that happen in the time gap between changing the source schema (step 1 above) and updating the value of `@capture_instance` (step 2). Try to keep the gap as short as possible or perform the update at a time when you expect -few changes to the data.{{< /note >}} \ No newline at end of file +few changes to the data.{{< /note >}} From 1a03e0df021512e86f2c2489ac6bd5c8290b2cba Mon Sep 17 00:00:00 2001 From: ilianiliev-redis Date: Wed, 16 Sep 2026 17:35:38 +0300 Subject: [PATCH 2/3] Update content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com> --- .../data-pipelines/prepare-dbs/sql-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md index 445d780aa8..e3ca0ebb9a 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md @@ -207,7 +207,7 @@ GO ## 5. Using SQL Server with custom data fields -When using custom data types, you need to ensure that the Debezium user has the necessary permissions to access +When using custom data types, you must ensure that the Debezium user has the necessary permissions to access those types. You can grant these permissions using the following SQL commands: ```sql From 43fa5920d50c049547e2b6138115748e924dd8aa Mon Sep 17 00:00:00 2001 From: ilianiliev-redis Date: Wed, 16 Sep 2026 17:35:50 +0300 Subject: [PATCH 3/3] Update content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com> --- .../data-pipelines/prepare-dbs/sql-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md index e3ca0ebb9a..61885fbb4b 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md @@ -216,7 +216,7 @@ USE ; GRANT REFERENCES ON TYPE::. TO ; ``` -Without granting these permissions you may encounter errors like: +If you don't grant these permissions you may encounter errors like: `"The column "Account" is referenced as PRIMARY KEY, but a matching column is not defined in table "DB.dbo.MyTable"!"`