Server Engine on a Windows Server
On Windows server environments, Pervasive PSQL Server runs as services. The services are loaded as part of the installation process and are set to be always available if you followed the default installation.
Services Dependencies
Additional Pervasive PSQL products such as Pervasive
DataExchange also install services. Pervasive DataExchange depends on both Pervasive PSQL Transactional Engine and Pervasive PSQL Relational Engine services.
The following table summarizes the behavior of the dependent services for start, stop, and restart actions of the database engine services.
Note that the behavior of the dependent services is the same regardless with which application you start, stop, or restart the database engine services (PCC, Windows Services, Net Start, PSC).
If you start the service for DataExchange, the Pervasive PSQL Relational Engine starts as a prerequisite service.
Note The dependent services stop without displaying a message that they will be stopped.
³ To start the database services on a Windows server using PCC
See “To start or stop services” on page 3-13.
³ To stop the database services on a Windows server using PCC
See “To start or stop services” on page 3-13.
Table 2-1 Action of Dependent Services Based on Action of Database Engine Services
Database Engine Service Start Stop Restart Service Action for Data Exchange Pervasive PSQL
Transactional Engine no action
Stop
Restart
Pervasive PSQL Relational
Engine no action
Stop
Restart
³ To start the database services on a Windows server using Control Panel
1 In the Windows Control Panel, double-click Administrative Tools then double-click Services.
A dialog box similar to Figure 2-1 appears.
Figure 2-1 Services Dialog Box
2 Right-click Pervasive PSQL Transactional Engine then click Start. Right-click Pervasive PSQL Relational Engine then click Start.
³ To stop the database services on a Windows server using Control Panel
1 In the Windows Control Panel, double-click Administrative Tools then double-click Services.
A dialog box similar to Figure 2-1 appears.
Figure 2-2 Services Dialog Box
2 Right-click Pervasive PSQL Relational Engine then click Stop.
Right-click Pervasive PSQL Transactional Engine then click Stop.
³ To start the database services on a Windows server by using Net Start or PSC
1 Click Start Run.
2 Type one of the following:
a. net start “Pervasive.SQL (<transactional | relational>)”
b. psc start “Pervasive.SQL (<transactional | relational>)”
3 Click OK.
³ To stop the database services on a Windows server by using Net Stop or PSC
1 Click Start Run.
2 Type one of the following:
a. net stop “Pervasive.SQL (<transactional | relational>)”
b. psc stop “Pervasive.SQL (<transactional | relational>)”
³ To start the Workgroup Engine as an application on Windows
These steps assume that the Workgroup Engine was installed as an application. See “Installing the Pervasive PSQL Workgroup for Windows” on page 6-3 in Getting Started With Pervasive PSQL.
1 Click Engines from the Pervasive group on the Start menu.
2 Click Start Workgroup Engine.
³ To stop the Workgroup Engine as an application on Windows
These steps assume that the Workgroup Engine was installed as an application. See “Installing the Pervasive PSQL Workgroup for Windows” on page 6-3 in Getting Started With Pervasive PSQL.
1 On the Windows taskbar, right-click the Pervasive Database icon: .
2 Click Stop Engines and Exit.
Note You will receive a warning message when trying to stop the engine if any of the following is true:
There are active clients.
No activity took place since the engine loaded.
10 seconds has not elapsed since the last operation took place.
³ To start the Workgroup Engine as a service on Windows
These steps assume that the Workgroup Engine was installed as a service. See “Installing the Pervasive PSQL Workgroup for Windows” on page 6-3 in Getting Started With Pervasive PSQL.
1 Refer to the various methods described in the section “Starting and Stopping the Server Engine on a Windows Server.”
2 Substitute “Pervasive PSQL Workgroup Engine” as the service name if you useWindows Services control panel. Substitute
“psqlWGE” as the service name if you use net start or psc.
³ To stop the Workgroup Engine as a service on Windows
These steps assume that the Workgroup Engine was installed as a service. See “Installing the Pervasive PSQL Workgroup for Windows” on page 6-3 in Getting Started With Pervasive PSQL.
1 Refer to the various methods described in the section “Starting and Stopping the Server Engine on a Windows Server.”
2 Substitute “Pervasive PSQL Workgroup Engine” as the service name if you useWindows Services control panel. Substitute
“psqlWGE” as the service name if you use net start or psc.
Starting and Stopping the Database Engine on Linux
In Linux, the database engine runs as a daemon. The daemon is loaded as part of the installation process and is set to be always available if you followed the complete installation.
You must be logged in as the root user to start and stop the Pervasive PSQL v10 SP3 daemon process. Use the shell script psql to start and stop the process.
³ To start the database engine on Linux Enter the following at the command line:
/etc/init.d/psql start
For Pervasive PSQL 64-bit Server, this command starts both the transactional daemon and the relational daemon. The relational daemon is 32-bit only.
³ To stop the database engine on Linux Enter the following at the command line:
/etc/init.d/psql stop
For Pervasive PSQL 64-bit Server, this command stops both the transactional daemon and the relational daemon.
³ To force stop the database engine on Linux
If the database engine does not start or stop correctly using the psql start and stop commands, you may need to force stop the engine.
The force stop removes any shared memory and semaphores created by Pervasive PSQL and stops the Pervasive PSQL relational and transactional processes. Enter the following at the command line to force stop the database engine:
/etc/init.d/psql force