---
title: "Set up maintenance parameters"
slug: "set-up-maintenance-parameters"
tags: ["Task", "Data Modeling Studio", "DMS"]
updated: 2026-03-20T08:19:34Z
published: 2026-03-20T17:44:45Z
canonical: "docs.staedean.com/set-up-maintenance-parameters"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up maintenance parameters

Several upgrade scripts are available to be used on upgrading your **Data modeling studio installation** to a newer version. Probably, most of these upgrade scripts aren't applicable anymore to must of the **Data modeling studio installations**.

The only one that can possibly be applicable is the **Upgrade post processing script** (updateStagingEntitySuffixScript). You can use this upgrade script if you upgrade your **Data modeling studio installation** from a version that's older than 10.0.25.... This script solves possible issues with the entity suffix.

Run the script after you have upgraded your **Data modeling studio installation** to the newest version.

You can also define some diagnostics-related settings.

### Steps

1. Go to **Data modeling studio** > **Data modeling studio** > **Parameters**.
2. Click the **Maintenance** tab.
3. Sub-task: Run upgrade script.
  1. In the list, find and select the **Upgrade post processing script** (updateStagingEntitySuffixScript).
  2. Click **Run selected script**.

> [!NOTE]
> **Note**
> 
> You can run the upgrade script only once. If it has run successfully (**Status**='**Success**'), the **Run selected script** button is disabled. Also, if you click **Run all scripts**, the scripts which **Status** is '**Success**' are not run.
4. Sub-task: Define diagnostics settings.
  1. By default, the metadata update actions are not logged. You can have the metadata update actions logged for diagnostics or troubleshooting purposes. You can review the logged metadata update actions on the **Data exchange monitoring** page.

Select **Yes** in the **Metadata caching** field.
  2. By default, on data export, SQL statements are only logged if an error occurs. For diagnostics or troubleshooting purposes, you can have all SQL statements logged on data export.

Select **Yes** in the **SQL execution** field.

> [!NOTE]
> **Note**
> 
> If you select '**Yes**', a dialog is opened where you can define the SQL statement logging settings.
  3. You can only have all SQL statement logged for a specific data model.

In the **Model name** field, enter or select a value.
  4. Optionally, you can have all SQL statements logged for only a specific entity (data set or data entity) of the defined data model.

In the **Data entity** field, type a value.
  5. As this additional logging lowers the performance of exports, usually, you activate logging of all SQL statements only for a limited number of data exports for a data model.

In the **Number of executions** field, enter a number.
  6. Click **OK**.
5. Close the page.

## Related

- [Set up parameters](/set-up-parameters-dsm.md)