Query Windows Service

The Query Windows Service handles all operations that involve only the Responder database. This decreases the amount of work going to Data Services and allows operations to be executed concurrently (Query Windows Service and Data Services). If you have created custom Request Objects that involve only the Responder active and/or history tables, you may implement a custom attribute that routes these objects through the Query Windows Service. This implementation should improve the response time for your request object.

First, determine whether your custom request object involves only the Responder active and/or history tables (NOT archive tables). Ensure the following:

The request object does not access any mapping workspace or service .
The request accesses or modifies the Responder active or history tables (i.e., it does NOT access or modify the Responder archive tables).

Next, your custom request object must use the Responder custom attribute, "UsesQueryServices", found in Miner.Responder.Shared. Add this attribute to the list of attributes for your custom request object. The client-side proxy which interfaces with Data Services will look for this attribute on the request object. If it is found, the request is routed to the Query Windows Service.