You can use the following SQL query to retrieve all information from the Stock table and publish events for each row returned from the SQL query:

The SQL query in the SQL source service results in three RulePoint events, one event for each row in the Stock table. Each event has four properties each, one for each column name in the Stock table. The SQL query extracts the same data every time it runs unless you constrain the query based on time, date, or some other criteria.

You can constrain the SQL query by defining a volume limit.

This SQL query results in two RulePoint events, one event for symbol ABCD and the other for symbol EFG. Each event has four properties each, one for each column name in the Stock table.

You can also constrain the SQL query by defining a limit in the table property.

The SQL query results in two RulePoint events for the first two rows retrieved from the Stock table. Each event has two properties, one each for Symbol and Price.

You can parameterize the SQL query and use the columns returned from the SQL query as inputs in the statement.

The parameter in the query is

recordtime

. You can define the parameter as a name-value pair. For example,

recordtime=06-NOV-12

.

The SQL query results in RulePoint events for all records from the Stock table that are saved after the

recordtime

.

The SQL Source service can be configured to pull only new or updated records from the database based on the last scheduled run of the SQL service. The filter to select only the updated records is built into the SQL query based on information retained and provided by the SQL source itself.

You can use the SQL query to select only unprocessed records.

In the following example, a stock table has a

processed_ind

column indicating which records have been processed,

F

for not processed and

T

for processed:

You can use the following SQL query to update the

id

if the

processed_ind

column is processed: