Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a table with a lot of rows. The structure is something like this:
UserID | ItemID | Item Data...
Would I see any gains in query time if I separated this into a table per user, or per smaller group of users?
Queries are always single user getting/modifying a selection of items.
Do not make multiple tables.
Tell us what you think “lots of rows” is.
Do you have any indexes or constraints on the table?
How is the data inserted, updated and deleted?
Typically, I would want a unique index on UserID, ItemID, but without knowing more about your environment, it’s hard to say.
Also, please give us information on the database platform and the data types you have chosen.