Pairing
Using the new MSSQL data source, large binary objects are automatically streamed directly from the database to the client web browser as appropriate without loading the document into memory first.
In order to allow file image handling and file downloads to be streamed without being loaded into memory first, an MSSQL data source can be paired with a Mongoose-based data source as part of the portal configuration. This indicates to the portal architecture that the MSSQL data source connects to the same database as the Mongoose-based data source does via its Mongoose Config.
When this is done, the Mongoose-based data source can bypass the Mongoose utility server when working with large binary objects to avoid the above mentioned memory issues.
Pairing configuration options
For pairing to work, the MSSQL data source must be associated with a Mongoose-based data source. In the Portal Manager, use this setting:
Paired Back Office Data Source: This field provides a list of all the Mongoose-based data sources currently available. If left blank, pairing is not enabled.
Similarly, the Mongoose-based data source must be associated with an MSSQL data source. Use this setting:
Paired MSSQL Data Source: This field provides a list of all the MSSQL data sources currently available. If left blank, pairing is not enabled.
When pairing is set up, the Mongoose-based data source uses the paired MSSQL data source instead of the utility server in situations where knowledge of the Mongoose-based schema allows it to by-pass the IDO.
These are situations in which this is the case:
- For access to back office attached documents
- For access to pictures for Items, Item Pictures, and Item Categories