Execute SQL - Performance Queries

  • Updated

Mission Control is currently in beta, which is open to all partners of Optimizely Configured Commerce and invite-only for some customers. If you do not have access to Mission Control, Optimizely Support can run these actions on your behalf. Contact them with the needed configuration details and field values (if applicable).

For information on the Mission Control beta or to request access, contact your Customer Success Manager.

You can run a canned set of performance queries in Mission Control against the target instance in Optimizely Configured Commerce to gauge page life expectancy and slow query performance on the instance.

Although it is unlikely, running this action could impact performance for the given instance if the queried dataset is large enough. This is especially true for high traffic instances (like a production site).

Steps

  1. Log into Mission Control.
  2. Go to Customers and select a customer.
  3. Select a target Configured Commerce instance.
  4. Click Actions on the instance page and select Execute SQL - Performance Queries.
  5. (Optional) Schedule the action by toggling Scheduled Execution to On and selecting a time and date.
  6. Review the details to confirm the selected instance (and scheduled time, if selected). You can ignore any greyed-out or immutable fields because they are for development or debugging.
  7. Click Continue. If scheduled, the action runs at the specified time. Otherwise, the action runs immediately.
  8. Wait until the status is marked as Complete on the Action Request page. The action outputs a download link to a file with the SQL results. See Review results for information.

    If the action fails, submit a ticket with Optimizely Support with a link to the failed action request page.

Review results

The results return as a link to download/view the resulting file(s). The file(s) are best viewed in an editor with word-wrap set to Off to contain the contents in the respective columns and display them in a readable format. Some columns word-wrap themselves sometimes due to the hard cap for a line/column length in sqlcmd.

The first query results determine which of the two performance queries (page life expectancy or slow queries) is most interesting. The second query is for page life expectancy, and the third is for slow queries.