Controlling Services for SQDR, Db2 for LUW and SQL Server

SQDR Service

SQDR runs as a Windows service. You can review the status and manage the Data Replicator service from the Windows Services Control Panel or from the Data Replicator Manager application. The Data Replicator service name is StarQuest Data Replicator (SQDRSVC).

When you start the Data Replicator Manager it automatically starts the Data Replicator Service. Closing the Replicator Manager does not automatically stop the Replicator Service or any Db2 or SQL Server services. This allows any replication operations that have been scheduled to run at their scheduled time. When the time comes to run the job (a subscription that has been scheduled from the Replicator Manager), the Replicator Service must be running.

Db2 for LUW

If you using Db2 for LUW for the SQDR control database, the Db2 service must be running for the Replicator Service to access its control database.

You can review the status and manage the Db2 service from the Windows Services Control Panel, from the Db2 system tray icon, or from a Db2 command line environment.

SQL Server

Similarly, if you are using SQL Server for the SQDR control database, the SQL Server service must be running for the Replicator Service to access its control database. You can start an instance of SQL Server automatically, manually, or from the command prompt. Both the automatic and manual methods start an instance of SQL Server as a Windows service.

Using Windows Services Control Panel

You can review the status and manage the SQL Server services from the Windows Services Control Panel. The default SQL Server service is named MSSQLSERVER. Named instances of SQL Server appear as MSSQL$instance_name.

Windows Services Control Panel

Refer to the SQL Server Books Online for detailed information about starting, stopping, and pausing the SQL Server components.