Components of the Catalog Database

The product catalog database is created when you unpack a Solution Site. A series of tables are created. These tables are used for general maintenance and operation of the database.

For detailed information about securing these tables, see Securing the Product Catalog Database.

Ee796586.note(en-US,CS.20).gifNote

  • Do not modify these core tables for any reason. They are provided here as an example.

When you begin creating a new product catalog, Commerce Server 2002 dynamically creates tables to facilitate storing the data for a new catalog. The following components are generated for a new catalog:

  • Base Catalog Tables
  • Virtual Catalog Tables
  • Language-specific Catalog Tables
  • Catalog-specific Stored Procedures
  • Catalog-specific Views
  • Full-text Search Indexes
  • MSCS_CatalogScratch Database

Base Catalog Tables

Following are the catalog tables that are used by a base catalog.

  • <CatalogName>_CatalogProducts
  • <CatalogName>_CatalogRelationships
  • <CatalogName>_CatalogHierarchy
  • <CatalogName>_CatalogDeletedProducts (Note that this table is not needed in a production environment.)
  • <CatalogName>_CatalogDependentCatalogs

Virtual Catalog Tables

When you create a virtual catalog, the following tables are dynamically generated by aggregating the catalog name, and the role of the table in supporting the catalog:

Ee796586.note(en-US,CS.20).gifNote

  • The following tables do not apply to the Adventure Works catalog scenario, which uses a base catalog only.
    • <CatalogName>_CatalogRelationships
    • <CatalogName>_CatalogHierarchy
    • <CatalogName>_CatalogProducts
    • <CatalogName>_CatalogDeletedProducts (Note that this table is not needed in a production environment.)
    • <CatalogName>_CatalogIncludedProductsAndCategories
    • <CatalogName>_CatalogPricingRules
    • <CatalogName>_CatalogVirtualProducts

Language-specific Catalog Tables

To support globalization of the product catalog, a language-specific table is created for each new language that is defined for the catalog:

  • <CatalogName>_<Language>_Catalog

In this example, you will work with a U.S. English table named AdventureWorksCatalog_en-US_Catalog.

Catalog-specific Stored Procedures

When a new catalog is created, Commerce Server 2002 creates the following stored procedures that relate specifically to the new catalog. The standard naming conventions for these stored procedures are as follows:

  • ctlg_DeleteProduct_for_<CatalogName>
  • ctlg_GetRelationships_for_<CatalogName>
  • ctlg_DeleteCategory_for_<CatalogName>

The language-specific stored procedures are:

  • ctlg_AncestorCategories_for_<CatalogName>_<language>
  • ctlg_GetCategoryResults_for_<CatalogName>_<language>
  • ctlg_GetProducts_for_<CatalogName>_<language>
  • ctlg_GetDescProds_for_<CatalogName>_<language>
  • ctlg_GetDescProdsOnly_for_<CatalogName>_<language>
  • ctlg_GetChildCategories_for_<CatalogName>_language>
  • ctlg_GetRootCategories_for_<CatalogName>_<language>
  • ctlg_GetRootProducts_for_<CatalogName>_<language>
  • ctlg_Specsearch_for_<CatalogName>_<language>

Catalog-specific Views

Several views are created for a new catalog. They follow the same naming convention as tables and stored procedures:

  • <CatalogName>_ClassTypes
  • <CatalogName>_LNG_NEUTRAL

The language-specific views for each language defined for the catalog are:

  • <CatalogName>_<Language>_RelationsView
  • <CatalogName>_<Language>_Catalog

Full-text Search Indexes

Product catalogs make use of SQL full-text search indexes that are dynamically created as part of a new catalog. The contents of these indexes will not be replicated but will be re-generated on the production database server.

The <CatalogName>_FullTextCatalog catalog is created to support a full-text index on the following catalogs:

  • <CatalogName>_CatalogProducts, which includes fields that are marked as searchable in Business Desk.
  • <CatalogName>_<Language>_Catalog for each language defined in the catalog. This table specifically includes the name and display name fields.

MSCS_CatalogScratch

The Product Catalog System uses a "scratch" database, MSCS_CatalogScratch, for storing temporary tables. You must ensure that this database exists on your production catalog database server(s) and that the CTLG_PropertyTableMap table is replicated.

For more information about this database, see MSCS_CatalogScratch.

Copyright © 2005 Microsoft Corporation.
All rights reserved.