Skip to main content

Re-Indexing a Database

When updating the databases used by FlexNet Manager Suite, consider whether this is also the time to re-index the databases. Take into account the following factors:

  • Re-indexing increases data access speed and recovers wasted disk space.

    Tip: It is a good idea to re-index your database at least once a year. In SQL Server, tables that do not have clustered indexes do not automatically reclaim space from deleted records. Re-indexing will reclaim this space.

  • Re-indexing is especially important if you have a lot of records in history tables. For example, in the inventory database, check the Installation and InstallationHistory tables.

  • Re-indexing is very demanding for SQL Server. You should only ever attempt a re-indexing of one database at a time. It is also good practice to schedule this out of production times, such as overnight or on a weekend.

  • On large databases, this process can take more than 24 hours.

There is no requirement that you must re-index at this time: you may prefer to complete the current processes and schedule re-indexing at appropriate times soon. However, your current process is an excellent trigger for planning a regular schedule for re-indexing, say one or twice a year.

FlexNet Manager Suite provides a re-indexing script that can be applied to the following databases:

  • The compliance database (suggested name: <Dbcomp />)
  • The inventory database (suggested name: FNMSInventory)
  • The data warehouse database (suggested name: FNMSDataWarehouse).

(There is little benefit in re-indexing the snapshot database (suggested name: FNMSSnapshot), as this is effectively cleaned up each time a snapshot is saved.)

Important: Do not apply the script to the Report Writer Content Store. This is a database designed by Cognos and not aligned with the reindexing script from Flexera.

  1. To re-index one of the FlexNet Manager Suite operations databases (optional):

  2. Start SQL Server Management Studio (or your preferred tool).

  3. Select one of the above three databases to reindex.

  4. Open the ReIndexAll.sql reindexing script from your unzipped archive (for example, C:\temp\FNMSDownloads\Database Migration\Normal).

  5. Click the Execute Query tool, or press F5 to run the script.

Keep in mind that the re-indexing of each database may take a considerable time, depending on the size of your database. Wait until each process has completed before looping back to repeat for another of the three applicable databases.

Parent topic:Upgrade/Create Databases