If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
do I need more indexes?
After reading several posts here I have changed all of the lookup fields to
text fields in my table and deleted the relationships to the lookup tables. I came to this area looking for a solution to slow response time. Again, after reading several posts, I suspect it is due to the database design, but it is what I have to work with. Other than the lookup tables, there are only two related tables. If it would be helpful, I can remove the lookup tables. tSample (with the major fields listed below) Key (primary key) CNTYNAME ID Strata Sample tReview ReviewKey (PK) Key (FK) A1 A2. . . B1 B2. . .(in total there are over 60 number fields and 50 memo fields). I read that creating indexes will increase response time. Will creating a unique index from two fields in addition to the PK increase response time (e.g., in tSample, a unique key comprised of CNTYNAME and ID)? All was going well for the individual county reports, but I had problems when an aggregate report was needed at year end. I was able to solve the problem with advice obtained through this site. First, I created a union query (qUnion); a crosstab query based on the union query (qUnionCrosstab); and combined qUnionCrosstab and qReviewCountCrosstab into one query (qCrosstabsCombined) for the aggregate report. The aggregate report is extremely slow to open and painfully slow in design view. Will it help to create additional indexes? If not, I can live with this report as it is since I only need it once a year. I don’t know how to change the design and transfer the data. Thanks for any tips for improvement. I am very grateful for the great information I have found here. |
Thread Tools | |
Display Modes | |
|
|