Jump to content

One table with milions records or many tables with thousand records?


GPT

Recommended Posts

Hello,

 

I have Events and Tickets​ tables.

 

In Tickets table I have at least the following fields:

 

EventsID

CustomersID​

TicketNo

...

 

The number of tickets for an event varies between 500-20,000. That means the number of records after 100 events may be 50,000-2,000,000.

 

I wonder if it is better for each event to have a different table, which means I have 100 tables with 500-20,000 records in each.

 

Which design is better for selecting/querying customers records?

 

Thanks in advance.

Edited by GPT
Link to comment
Share on other sites

It's never a good idea to dynamically create tables. Database are designed to handle millions of records, so I would recommend having just one table for the tickets.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...