title: DB tables design with a lot of attributes
body: <p>I'd like to know how the db design should look like in this case.</p>
  
  <p><img src="https://i.stack.imgur.com/Zw7jT.png" alt="enter image description here"></p>
  
  <p>What comes to my mind is a table for every entity like:  </p>
  
  <pre><code>Engine  
  EngineDesign  
  ElectricalSystem  
  Drivetrain  
  etc.
  </code></pre>
  
  <p>But it looks to me as a lot of tables. Is my idea ok or is it excessive?</p>
  
  <p>And what about the Drivetrain? Today we have 8 gears but it can change whenever a manufacturer comes with something different.</p>
  
  <p>Should it be like this:<br>
  Table (columns)  </p>
  
  <pre><code>DrivetrainId | 1st | 2nd | 3rd | etc.
  </code></pre>
  
  <p>Or</p>
  
  <p>Table (rows)  </p>
  
  <pre><code>DrivetrainId | Gears
  1            | 1st
  2            | 2nd
  3            | 3rd
  etc.
  </code></pre>