| Prev | Next |
Re-Index a Firebird Project
After a period of time, through general use, a Firebird-based project file can develop non-optimized indexes, causing data retrievals to be slow and affecting the general performance of Enterprise Architect while using that repository.
To resolve such issues you can move the project to a local drive and request the database engine to rebuild all indexes the next time they are used; this is referred to as Updating the Statistics of the Indexes.
Access
|
Ribbon |
Settings > Model > Integrity > Manage Firebird > Update Index Statistics |
Index a Firebird Project
Step |
Action |
|---|---|
|
1 |
Open the Firebird project to re-index. |
|
2 |
Ensure no other users have the file open. |
|
3 |
Select the 'Update Index Statistics...' option. |
|
4 |
Follow the on-screen instructions to complete the process. |
Notes
- The process to re-index a project should always be performed on a local drive, never on a network drive
- Over the years Sparx Systems have improved the default indexes that are defined within an Enterprise Architect repository, so whenever a new .EAP/EAPX is created it will be created with the latest indexes; however, if a .EAP/.EAPX repository has been in use for many years then the defined indexes are most likely not ideal, but you can use another ribbon option - 'Update .EAP and .EAPX file indexes' - to remove all old indexes and generate the latest index definitions
- In the Corporate, Unified and Ultimate Editions of Enterprise Architect, if security is enabled you must have 'Administer Database' permission to re-index a project