ERD Model Toss-up

[DevTycoon]

Hi All,

I need to create a database that can track different manufacturer’s catalog. In a sense, make my own catalogue of other catalogues. Each manufacturer does things a little different but the parts being tracked are ASME certified so they function the same way. They just have different designs, component materials, sizing, etc. There are two ERD's I am looking at and am a little confused. Anyone have some input on these two options or perhaps one I have overlooked?

Thanks

-Devy

Simple Model
http://www.databaseanswers.org/data_models/product_catalogs/index.htm

Complex-More Flexibility Model
http://www.databaseanswers.org/data_models/product_catalogs/complex_product_catalogs.htm

 

[MarkK]

Those are examples, and we can't recommend one without knowing your exact purpose. The structure you need is based on the job you need to do. Those designs, for instance, essentially store the "chapter" of the catalog in their "Catalog_Structure" table. Do you need that? Will you ever have a product that contains another product or quantity of products? If you have products with a fixed list of attributes or properties then go with the simple model. If you'll have an extremely varied product line, with lists of attributes that are not shared from product to product, go with the more complex model.

But again, your needs should inform the structure, so what, exactly, are your needs? Don't implement features that don't need to be handled in YOUR data.

 

[DevTycoon]

Those are examples, and we can't recommend one without knowing your exact purpose. The structure you need is based on the job you need to do. Those designs, for instance, essentially store the "chapter" of the catalog in their "Catalog_Structure" table. Do you need that? Will you ever have a product that contains another product or quantity of products? If you have products with a fixed list of attributes or properties then go with the simple model. If you'll have an extremely varied product line, with lists of attributes that are not shared from product to product, go with the more complex model.

But again, your needs should inform the structure, so what, exactly, are your needs? Don't implement features that don't need to be handled in YOUR data.

Ok thanks Markk.