The syntax of Configure System to configure Phased versus Non-Phased SQL for database reads is
ConfigureSystem /PS /S <SystemName> [/PO <true|false>] [/PR <true|false>][/ISP <IspecName>] [/ISV <true|false>] [/RPT <ReportName>] [/RPV <true|false>][/ ]
When you use Phased SQL with the various Determine commands, the retrieval of records happens in a series of phases, with one SQL SELECT statement submitted for each phase. The number of phases or the number of SQL SELECT statements is dependent on the number of keys used on a profile and the type of Determine command. If you use Non-Phased SQL with various Determine commands, a single SQL SELECT statement is constructed to retrieve all records. This implies that a Non-Phased SELECT statement have a more complex WHERE clause.
If you pass valid parameters, the message "Successfully updated the configuration" appears. The DBConfig.xml file available at the Data\Public folder is automatically updated with the values set in the arguments.
Note: If you are configuring AB Suite runtime with the Phased SQL versus Non-Phased SQL feature for the first time, the DBConfig.xml file with the configuration is created in the Data\Public folder location.
Parameters
Argument | Description |
---|---|
/PS <ViewName> | Specifies configuring a runtime system to use the Phased SQL versus Non-Phased SQL feature for retrieving data through the Determine commands. Note: This argument is mandatory. If you do not pass this argument, the error message "Mandatory Input Missing or Invalid: /PS /S " appears. |
/S <SystemName> | Specifies the name of a deployed system for which the Phased SQL versus Non-Phased SQL behavior can be defined. Notes:
|
/PO <true|false> | Specifies enabling or disabling the Phased SQL behavior for all the Determine commands across the system. Note: If no value or an invalid value is passed with this argument, the error message Invalid argument<s> : /PO" appears.
For example: To set Non-Phased SQL for the whole online system, type ConfigureSystem /PS /S Sample /PO false |
/PR <true|false> | Specifies enabling or disabling the Phased SQL behavior in all reports. Note: If no value or an invalid value is passed with this argument, the error message Invalid argument<s> : /PR" appears. For example: To set Phased SQL in reports only, type ConfigureSystem /PS /S Sample /PO false /PR true |
/ISP <IspecName> | Specifies a specific ispec name where Phased SQL can be enabled. Note: If you do not pass an ispec name for which the Phased SQL value is specified by setting the /ISV argument, the error message "Error: Ispec value/name is missing" appears. |
/ISV < true|false > | Specifies enabling or disabling the Phased SQL behavior for the ispec stated in the previous argument. Notes:
For example: To set Phased SQL in the SALE ispec, type: ConfigureSystem /PS /S Sample /ISP SALE /ISV true |
/RPT <ReportName> | Specifies an individual report name where the Phased SQL behavior can be enabled. Note: If you do not pass a report name for which the Phased SQL value is set through the /RPV argument, the error message "Error: Report value/name is missing" appears.
|
/RPV <true|false> | Specifies enabling or disabling the Phased SQL behavior for the report stated in the previous argument. Notes:
For example: To set Phased SQL in the PRODSTATS report, type ConfigureSystem /PS /S Sample /RPT "PRODSTATS" /RPV true |
/PS / | Displays command line syntax for setting the Phased SQL versus Non-Phased SQL behavior and arguments of the utility. If specified, a usage message displays, and the utility exits without starting the configuring process. |