Index | Prev | Next

Optimizing pre- Niagara 4.11 database tables

If your archived histories predate Niagara 4.11, you may choose to run a job that optimizes your relational database’s existing table indexes. Once optimized, you do not need to perform this optional index migration again in the future. It is not required and has no impact on the functionality of the Rdb Archive History Provider, but you may notice that the history query performance is not optimal when the indexes are not present and/or migrated.
Prerequisites: You are working in Workbench running on a PC, are connected to a Supervisor station and have access to a relational database on your company’s network.
Although this step is not required, optimizing the existing table indexes can maximize query performance. Since this procedure affects the tables in the remote relational database, consult your DBA (Database Administrator) to make sure that your database has available space to add indexes if they are not already present. It is also recommended that you back up your database before you perform the migration in case a failure occurs during index migration.
Perform the following steps:
  1. In the Nav tree, expand Config > Drivers > RdbmsNetwork, expand your RDB node, right-click Histories and click Actions > Migrate to Optimized Data Indexes.
    The driver prompts you to confirm that you intend to run this job.
  2. To continue, click Yes.
    Invoking this action kicks off a job in the JobService where you can monitor the migration progress and see the results.
  3. To monitor job status, navigate to Config > Services and double-click JobService.
    The Job Service Manager opens and displays a row for Rdbms Migrate Indexes.
    Image

Related Links

  • Rdb Archive History Provider (Parent Topic)

    • Index | Prev | Next