Is this database model a good one?
I am building a vehicle maintenance application. In the application, every vehicle may have different types of services associated to it such as "Oil change every 10000Km" or "Radiator cleaning every 5,000Km". The types of services are defined in a ServiceType table and then associated to every vehicle.

Basically, the associating table can simply have the VehicleID and ServiceTypeID to do the association. But then, if I have say 1,000 vehicles and 4 service types for each, that means 4,000 records in that table.

I have two questions:

1. What might be a better way to model this

2. How can I determine when, performance wise, such a table would be too big? (if used this approach)

Thanks

Is this database model a good one?
===

I am building a vehicle maintenance application. In the application, every vehicle may have different types of services associated to it such as "Oil change every 10000Km" or "Radiator cleaning every 5,000Km". The types of services are defined in a ServiceType table and then associated to every vehicle.

Basically, the associating table can simply have the VehicleID and ServiceTypeID to do the association. But then, if I have say 1,000 vehicles and 4 service types for each, that means 4,000 records in that table.

I have two questions:

1. What might be a better way to model this

2. How can I determine when, performance wise, such a table would be too big? (if used this approach)

Thanks
