I’m working on a jewelry e-commerce project and need advice on designing an efficient SQL Server database structure. The store will include categories like engagement rings, wedding bands, and other jewelry products, along with features like product attributes, pricing, stock management, and customer orders.
Here are some key points I’m considering:
- Should I use separate tables for product categories (like engagement rings and wedding bands), or store everything in a single table with category attributes?
- What’s the best way to handle multiple attributes such as ring size, metal type, gemstone, and price variations?
- How can I ensure scalability for future product additions without redesigning the schema?
If anyone has experience designing databases for e-commerce or similar use cases, I’d appreciate your recommendations or any sample schema.