Database Design

The database is comprised of a single reference table for schedule information

• RaceCard
  • course
  • horse

Schedule information inserted to the RaceCard table may be assigned and recorded as an ID value instead of its Name. Storing recurring data this way increases query speed, strengthens data integrity whilst reducing storage capacity and redundancy across the dataset. The assigned ID is indexed against a Name within a dependant table.

dbo.distance insert procedure converts the race distance string to meters and furlongs

Scalar-valued-Functions support unit conversions and price statistics

RaceCard joins dependant tables > Join_RaceCard

---

RaceCard is depended on by other tables for schedule information

• RaceCard
  • PlacePrice
  • OtherPlace
  • Records

dbo.PlacePrice and dbo.OtherPlace record price information by respective market

dbo.Records records bet outcomes

These are dependant on dbo.RaceCard for schedule information

RaceCard joins PlacePrice > Join_PlacePrice

RaceCard joins Records > Join_Records

See Betting Records