Skip to main content
deleted 2 characters in body
Source Link

So there is one primary key so far used for IDs of locations.

Currently there are multiple tables (sheets) in Excel for the following

  • HolidaysEvents (Location ID, Date, Title, Description)
  • Animals (Location ID, Species, Name, Population)
  • Restrictions (Location ID, Permits, Zone)

Is the above bad practice? From what I have read online you should not use the same primary key across multiple tables.

How should the tables be structured to follow "best practices", have it be one big database table or is it fine to leave in multiple tables?

So there is one primary key so far used for IDs of locations.

Currently there are multiple tables (sheets) in Excel for the following

  • Holidays (Location ID, Date, Title, Description)
  • Animals (Location ID, Species, Name, Population)
  • Restrictions (Location ID, Permits, Zone)

Is the above bad practice? From what I have read online you should not use the same primary key across multiple tables.

How should the tables be structured to follow "best practices", have it be one big database table or is it fine to leave in multiple tables?

So there is one primary key so far used for IDs of locations.

Currently there are multiple tables (sheets) in Excel for the following

  • Events (Location ID, Date, Title, Description)
  • Animals (Location ID, Species, Name, Population)
  • Restrictions (Location ID, Permits, Zone)

Is the above bad practice? From what I have read online you should not use the same primary key across multiple tables.

How should the tables be structured to follow "best practices", have it be one big database table or is it fine to leave in multiple tables?

Source Link

Is it better to have multiple tables with the same primary key or one big data table?

So there is one primary key so far used for IDs of locations.

Currently there are multiple tables (sheets) in Excel for the following

  • Holidays (Location ID, Date, Title, Description)
  • Animals (Location ID, Species, Name, Population)
  • Restrictions (Location ID, Permits, Zone)

Is the above bad practice? From what I have read online you should not use the same primary key across multiple tables.

How should the tables be structured to follow "best practices", have it be one big database table or is it fine to leave in multiple tables?