SQL Server-一对一关系最佳实践

Question

I have a table called Station with many fields, one of the fields is - StationPrice.

I want to hold more information about the payment process such as - currency, paymentStatus and etc (somewhere like 10 fields). My question is if I need to expand the current table - Station with the new fields or to have a field called - StationPriceId that will be a foreign key to another table called StationPrices which will store all the information about the price related to that station.

Answer 1

The answer to your question is 1 of the most popular answers in DB world - it depends . It might look nicer if this info is split into 2 different tables, however you need to understand that if you split it then you'll need to 2 inserts instead of 1, the same with updated and deletes. Moreover you'll need to JOIN this table every time you'll need this data. I would go with single table first and then moved it to the separate column when the specific need come up.

From other side of view, if this data will be rarely accessed and JOIN/DELETE/INSERT overhead will be minimal then it is OK to move it.

Answer 2

My question is if I need to expand the current table - Station with the new fields or to have a field called - StationPriceId that will be a foreign key to another table called StationPrices which will store all the information about the price related to that station.

Yes it is better to use two tables, Based on information you had provided - it is better to use a separate table.

1. You might want to maintain a price change history
2. Hence if you maintain a separate table, you can make earlier price as Active = false and enter a new price for the particular station