Last modified: March 09, 2015
Applies to: Windows | Windows Server
The JetStopService function prepares an instance for termination.
JetStopService is the legacy call when only one instance is allowed. In this case, the only active instance is the one being prepared for termination.
JET_ERR JET_API JetStopService(void);
This function has no parameters.
This function returns the JET_ERR datatype with one of the following return codes. For more information about the possible ESE errors, see Extensible Storage Engine Errors and Error Handling Parameters.
The operation completed successfully.
It is not clear which instance to prepare for termination when using JetStopService with multiple instance mode.
Windows XP: This return value is introduced in Windows XP.
If this function succeeds, it prepares for a future termination. The steps taken to prepare for a termination include the following:
Stop online defragmentation if it is running.
Start a version store clean-up.
Reduce the checkpoint depth by starting to flush dirty pages in the buffer manager.
Prevent future calls to most functions for that instance.
If this function fails, none of the steps to prepare for an instance termination will be taken, so no change to the instance state will occur.
This function reduces the work the instance will have to do when terminated, but will not terminate the instance. As a result, this function is just an optimization and is not mandatory to use. Note that the amount of work done in preparation was less in Windows 2000 and Windows XP. Once the function succeeds, calling functions that are no longer allowed will return JET_errClientRequestToStopJetService. Functions that are still allowed after this call are: JetRollback, JetCloseTable, JetEndSession, JetCloseDatabase, JetDetachDatabase and JetResetSessionContext.
Requires Windows Vista, Windows XP, or Windows 2000 Professional.
Requires Windows Server 2008, Windows Server 2003, or Windows 2000 Server.
Declared in Esent.h.