Subject | deactivate indices |
---|---|
Author | rsalt12345 |
Post date | 2004-08-25T12:27:17Z |
I needed to use the gbak -I switch (deactivate indices) to restore a
client's database that contained foreign key violations. I corrected
this data problem and assumed that backing up & restoring (omitting
the -I switch) would reactivate the indexes but it didn't.
I have duplicated this on some test data as follows:
1. In ibexpert I ran a simple query joining 3 tables on primary key
fields and the performance analysis showed indexed reads (as
expected)
2. gbak'd database
3. restored database using the gbak -I switch
4. In ibexpert I ran same query as in point 1 and the performance
analysis shows ALL NON-indexed reads (as expected)
5. gbak'd database
6. restored database (omitting the gbak -I switch)
4. In ibexpert I ran same query as in point 1 and the performance
analysis STILL shows ALL NON-indexed reads !?
I'm sure I am missing something obvious here!
Any help much appreciated.
client's database that contained foreign key violations. I corrected
this data problem and assumed that backing up & restoring (omitting
the -I switch) would reactivate the indexes but it didn't.
I have duplicated this on some test data as follows:
1. In ibexpert I ran a simple query joining 3 tables on primary key
fields and the performance analysis showed indexed reads (as
expected)
2. gbak'd database
3. restored database using the gbak -I switch
4. In ibexpert I ran same query as in point 1 and the performance
analysis shows ALL NON-indexed reads (as expected)
5. gbak'd database
6. restored database (omitting the gbak -I switch)
4. In ibexpert I ran same query as in point 1 and the performance
analysis STILL shows ALL NON-indexed reads !?
I'm sure I am missing something obvious here!
Any help much appreciated.