We're populating a table with over 9 million addresses. These addresses serve an auto-complete lookup. Whenever a user starts typing, the lookup displays results that match what the user typed thusfar. This worked great when we had 10 addresses in the database. Now that the database is filled with over a million addresses, the lookup grinds to a halt whenever the user starts to type, uses the caret or clicks the looking glass to open the selection form. How do we handle tables containing a large amount of records with an auto-complete lookup?
The database is still getting filled. Once filled, we'll create an index on the table. This will speed it up. What other things can we do to keep the UI user-friendly and responsive? Can the looking glass and/or the caret be removed from the field, for instance?
We're using Universal, but the Windows GUI suffers from the same lag. Our database is an Azure hosted database.