Skip to content

Commit fc970e2

Browse files
DOC-4551 added SQL Server Agent troubleshooting note
1 parent c7d2d08 commit fc970e2

File tree

1 file changed

+27
-0
lines changed
  • content/integrate/redis-data-integration/data-pipelines/prepare-dbs

1 file changed

+27
-0
lines changed

content/integrate/redis-data-integration/data-pipelines/prepare-dbs/sql-server.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,33 @@ Follow the steps below to run `sys.sp_cdc_help_change_data_capture`:
131131
access. If the result is empty then you should check that you have privileges
132132
to access both the capture instance and the CDC tables.
133133

134+
### Troubleshooting
135+
136+
If no CDC is happening then it might mean that SQL Server Agent is down.
137+
You can check for this using the SQL query shown below:
138+
139+
```sql
140+
IF EXISTS ( SELECT 1
141+
FROM master.dbo.sysprocesses
142+
WHERE program_name = N'SQLAgent - Generic Refresher')
143+
BEGIN
144+
SELECT @@SERVERNAME AS 'InstanceName', 1 AS 'SQLServerAgentRunning'
145+
END
146+
ELSE
147+
BEGIN
148+
SELECT @@SERVERNAME AS 'InstanceName', 0 AS 'SQLServerAgentRunning'
149+
END
150+
```
151+
152+
If the query returns a result of `0`, you need to need to start
153+
SQL Server Agent using the following commands:
154+
155+
```sql
156+
EXEC xp_servicecontrol N'START',N'SQLServerAGENT';
157+
GO
158+
```
159+
160+
134161
## SQL Server on Azure
135162

136163
You can also use the Debezium SQL Server connector with SQL Server on Azure.

0 commit comments

Comments
 (0)