Skip to content

Improving SQL Server setup documentation when using custom types #3998

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ilianiliev-redis wants to merge 3 commits into
base: main
Choose a base branch
from
+16 −1
Open

Improving SQL Server setup documentation when using custom types #3998

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
913cd87
Improving SQL Server setup documentation when using custom types
ilianiliev-redis Sep 14, 2026
1a03e0d
Update content/integrate/redis-data-integration/data-pipelines/prepar…
ilianiliev-redis Sep 16, 2026
43fa592
Update content/integrate/redis-data-integration/data-pipelines/prepar…
ilianiliev-redis Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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
USE <db-name>;

GRANT REFERENCES ON TYPE::<schema>.<type-name> TO <db-user>;
```

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"!"`


## SQL Server capture job agent configuration parameters

In SQL Server, the parameters that control the behavior of the capture job agent
Expand Down Expand Up @@ -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 >}}
few changes to the data.{{< /note >}}
Loading