title: Database design - do I need one of two database fields for this?
body: <p>I am putting together a schema for a database. The goal of the database is to track applications in our department.  I have a repeated problem that I am trying to solve.</p>
  
  <p>For example, I have an "Applications" table.  I want to keep track if any application uses a database or a bug tracking system so right now I have fields in the Applications table called</p>
  
  <p>Table: <strong>Applications</strong><br>
  UsesDatabase (bit)<br>
  Database_ID (int)<br>
  UsesBugTracking (bit)<br>
  BugTracking_ID (int)  </p>
  
  <p>Table: <strong>Databases:</strong><br>
  id<br>
  name  </p>
  
  <p>Table: <strong>BugTracking:</strong><br>
  id<br>
  name  </p>
  
  <p>Should I consolidate the "uses" column with the respective ID columns so there is only one bug tracking column and only one database column in the applications table?</p>
  
  <p>Any best practice here for database design?</p>
  
  <hr>
  
  <p>NOTE: I would like to run reports like "Percent of Application that use bug tracking" (although I guess either approach could generate this data.)</p>