Physical Schema Changes to a Staging Database

  • Article

Using SQL Server replication is not recommended for replicating catalog schema or the underlying physical catalog. Only use SQL Server replication for transferring content.

The following tasks result in changes to the underlying physical schema. To update a production environment with these changes, you must use a manual process, as follows:

  • Creating a new catalog. If you create a catalog in the publisher database, changes to the global catalog are replicated but the tables, views, and stored procedures are not replicated (this is a SQL Server restriction).
  • Deleting a catalog.
  • Adding a language to a catalog.
  • Deleting a language from a catalog.
  • Adding a property to a product definition (if the property is not already used in the catalog where the product definition is used).
  • Removing a property from a product definition (such that the property is no longer used in the catalog where the product definition is used).
  • Adding the first instance of a product of a particular product definition to a catalog (such that a particular property becomes used in that catalog).
  • Deleting the last instance of a product of a particular product definition from a catalog (such that a particular property is no longer used in that catalog).

If any of these types of changes are to be made to the staging catalog, then you will first need to drop the database publication and then set up replication again after these changes are completed.

Copyright © 2005 Microsoft Corporation.
All rights reserved.