R
ReidarT
How many fields can be indexed in a table, and what happens if you index
more fields than "maximum"?
regards
reidarT
more fields than "maximum"?
regards
reidarT
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Jeff Boyce
Reidar
Please pardon the seeming impertinence, but why do you want to know?
How many are you trying to index? Given that adding an index increases the
database size and slows response time for data entry work, why do you
believe you need a (potentially) large number of indexes?
Access won't allow you to set more than the maximum number of indices, which
you can look up in Access HELP under "specifications" -- I believe the
numbers are a max of 10 fields in an index and 32 indices in a table.
Good luck
Jeff Boyce
<Access MVP>
Please pardon the seeming impertinence, but why do you want to know?
How many are you trying to index? Given that adding an index increases the
database size and slows response time for data entry work, why do you
believe you need a (potentially) large number of indexes?
Access won't allow you to set more than the maximum number of indices, which
you can look up in Access HELP under "specifications" -- I believe the
numbers are a max of 10 fields in an index and 32 indices in a table.
Good luck
Jeff Boyce
<Access MVP>
J
John Vinson
How many fields can be indexed in a table,
32 indexes (each index can contain one to ten fields, though).
and what happens if you index
more fields than "maximum"?
You get an error message and you don't get the 33rd index.
T
TC
... and what happens if you index more fields than "maximum"?
If you could index more fields than the maximum, it wouldn't be a "maximum",
would it!
TC
G
Guest
Thanks for answers.
I thought 10 indexes was the most, but see it is possible
to use more than that.
I use a combobox to look up records from the "indexed"
table and wondered if the speed had something to do with
the number of indexes
regards
reidarT
I thought 10 indexes was the most, but see it is possible
to use more than that.
I use a combobox to look up records from the "indexed"
table and wondered if the speed had something to do with
the number of indexes
regards
reidarT
B
Baisong Wei[MSFT]
Hi Reidar,
Merry Christmas and thank you for using MSDN Newsgroup! It's my pleasure to
assist you with your issue.
So, you have a combo box, the row is from a table ( or a query ), you
wonder if if have indexes in the talbe could speed up and the more indexes
the table has, the faster it will be, right?
Here is some techniques for your to use index on you table.
1) There may be no performance improve for very small tables.
If you have just five records in a table, there may be no difference to
have or have no index on it. Because the the index information will be
saved in a specific structure. When retrieve data from a indexed table, it
will search this structure first, then get the data.
2) For a query, just as your combo box get data from the table, if you
choose all the records in a table, one index is enough. You'd better choose
the short, high selectivity and less frequently modified field(s) as your
index. For example, if you have a table of employee include EmployeeID,
LastName, FirstName, Gender, Address. The EmployeeID is the best choice.
3) For a specific query, such as 'select FirstName form Your_Table where
......', to have an index on field 'First Name' will cause the speed
faster. Because this will cover the query. In gereral, the filters in the
where clause will determine which indexes will be most useful.
Hope this information useful to your question. If you still have questions.
Please feel free to post new message here and I am ready to help!
Happy New Year!
Best regards
Baisong Wei
Microsoft Online Support
Merry Christmas and thank you for using MSDN Newsgroup! It's my pleasure to
assist you with your issue.
So, you have a combo box, the row is from a table ( or a query ), you
wonder if if have indexes in the talbe could speed up and the more indexes
the table has, the faster it will be, right?
Here is some techniques for your to use index on you table.
1) There may be no performance improve for very small tables.
If you have just five records in a table, there may be no difference to
have or have no index on it. Because the the index information will be
saved in a specific structure. When retrieve data from a indexed table, it
will search this structure first, then get the data.
2) For a query, just as your combo box get data from the table, if you
choose all the records in a table, one index is enough. You'd better choose
the short, high selectivity and less frequently modified field(s) as your
index. For example, if you have a table of employee include EmployeeID,
LastName, FirstName, Gender, Address. The EmployeeID is the best choice.
3) For a specific query, such as 'select FirstName form Your_Table where
......', to have an index on field 'First Name' will cause the speed
faster. Because this will cover the query. In gereral, the filters in the
where clause will determine which indexes will be most useful.
Hope this information useful to your question. If you still have questions.
Please feel free to post new message here and I am ready to help!
Happy New Year!
Best regards
Baisong Wei
Microsoft Online Support