Practising my SQL by creating an SQL for a grocery store.
Had a question related to performance for scanning a product portion.
Would the performance be significantly better organizing tables that hold only the necessary information for queries?
Or would the performance be negligible if I had one table that held all information related to a product?
ex.
product(barcode, department, product name, price, on sale, sale price, isle, vendor, quantity, unit, product recall, etc all info related to product)
vs
product(barcode, product name, price, on sale, sale price, product recall) productInfo(barcode, department, isle, vendor, quantity, unit, etc all info related to product)
I’m unsure if scanning comes to a crawl based on the amount of product the SQL holds.
As I’m sure the query will become much harder to work with on the backend as I start to have more and more tables.
Would I run into performance issues in the future if I had only table that held all product information?
Jaewoo Kim is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.