Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SergioM
Posting Yak Master
170 Posts |
 Posted - 2012-06-12 : 12:54:04
|
| I receive inventory feeds from distributors for stock that I want to resell. I heard somewhere that the data (though received in one feed) should be divided into two tables. I don't know if this is standard/correct, so I wanted to ask here.As I am told, one table should hold data that does not change. Such Product data would include; UPC, Manufacturer, Model, Title, Description, etc.Then a Separate table should be created for things that will change regularly. Such Inventory data would include; Price, Quantity, Item Condition, Return Policy, MSRP, MAP, etc...Does this make sense? Or is it all generally kept in one place, with only select rows updated? |
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2012-06-12 : 14:25:00
|
| depends what you want to do. there is no such thing as "keep it in one place" and "keep it separately". Really depends what it is you are trying to accomplish. What you describe as having being told sounds like a data warehouse Fact and Dimension type of stuff to me. Is that what you want to do? If so read up on data warehousing principles. What you have been told is good if you want to keep audit or a history of price and quantity and condition because these things change of course. If your manager wants a report that says "On January 15, 2011 how many items in our inventory were of condition = Excellent and then how many of these stayed Excellent on January 15, 2012" then you do need to separate it. If you do not care at all about that kind of stuff then you do not need to separate it. But I most definitely see the value of having this type of data.<><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
 |
|
|
|
|
|
|
|
Standard Method for dividing Data? (Not Technical)