JDBCProbe A JDBC probe runs on the MID Server to query an external database via [JDBC] and returns results to ServiceNowServiceNow. About this task Probes interact with the MID Server via the ECC Queue, therefore the response of a JDBC probe returns as an XML payload in an "input" ECC Queue record. By default, each response payload will contain up to 200 returned rows, this value can be modified by setting the probe parameter jdbcprobe_result_set_rows to the desired number. Activating the Plugin Contact Customer Support to activate the Integration - JDBC (com.snc.integration.jdbc) plugin. Procedure Navigate to System Definition > Plugins. Right-click the plugin name on the list and select Activate/Upgrade. If the plugin depends on other plugins, these plugins and their activation status are listed. [Optional] Select the Load demo data check box. Some plugins include demo data—sample records that are designed to illustrate plugin features for common use cases. Loading demo data is a good policy when first activating the plugin on a development or test instance. You can load demo data after the plugin is activated by repeating this process and selecting the check box. Click Activate. Direct JDBC ProbeA direct JDBC probe specifies all the parameters necessary in the outbound ECC Queue XML payload.JDBC Probes via Data SourceJDBC probes are executed via a JDBC data source when an import is running against the data source.Select * JDBC Probe short cutAlternatively, you may specify a table_name parameter instead of a work element and the following query could be executed.ParametersThe following parameters are available in a direct JDBC probe.Using the Work ElementThe work element encodes SQL statements to be executed by the probe.