<div>
We currently run a commercial shopping cart that has three tables for categories, #1 category table, #2 category Parent table, #3 category Node table. It's giving me a headache trying to figure out the relations. The main category table has most of the category information, the other two are just relational fields, an example: CategoryID, CatalogNodeID, CatalogNodeTypeID, etc...<br />
This design works fine for the shopping cart, but for the classifieds database we are developing, I'm not sure this is the best design for performance.<br />

</div>


<div>
<div class="content wysiwyg-content">
What is the best design for SQL data tables for Categories, Unlimited Sub-Categories, and Products? Some products will be in multiple categories. Also, what would be the best way to pull them out, Stored Procedures? Example code? (this will be for a classified ads website)<br />
Thanks for your time, it is very much appreciated!<br />
Dave
</div>
</div>


What is the best design for SQL data tables for Categories, Unlimited Sub-Categories, and Products? Some products will be in multiple categories. Also, what would be the best way to pull them out, Stored Procedures? Example code? (this will be for a classified ads website)
Thanks for your time, it is very much appreciated!
Dave

Categories/Sub-Categories - Best Performance? (ASP.NET / SQL)

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.

Microsoft SQL Server 2005

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.