title: Should I put optional record properties in a separate table?
body: <p>I have a table of about 1,000 records.  Around half of them will utilise a set of fields containing certain characteristics.  There's about 10 relevant fields.  The other half of the records won't need that information filled in.</p>
  
  <p>This table is central to the database and will be taking the bulk of the operations.  Though at only around 1,000 records, it's not much.</p>
  
  <p>The hardware that the database is stored on is old and slow (spinning hard drive not SSD... ) so I want to have a fairly optimised structure to make the most of it.  Obviously the increased size of the database alone due to the blank fields isn't a major concern, but if it's slowing down queries then that's not good.</p>
  
  <p>I guess I should describe the setup.  Currently Access 2007 client and Access backend, though the backend will soon move to SQL server.  Currently the backend is on the main server rack, but when moved to SQL Server it will get its own older server rack.</p>
  
  <p>So should I make a separate table to store the aforementioned set of characteristics, or should I leave it as is?</p>