mzzm

CS2002 (SP2 + Feature Pack 1)

I am working with a client that is planning on migrating 6 base
catalogs into one. There will continue to be some virtual catalogs off
of the single base catalog. The concerns are in what happens to the
data warehouse and reports. The site has been collecting data (orders,
products, web logs) for nearly a year and they don't want to lose their
data. All of the products will continue to reside in the new base
catalog and the previous base catalogs will simply be the top level
category in the new base catalog.

Questions:

What happens to the current data warehouse? Can I simply rebuild the
entire data warehouse?

What happens to the reports? Which stock reports are affected?

What should I be concerned with in the migration of data?

What tables do I need to manually write SQL scripts for in order to
update from the previous to the new catalog?

What steps should I follow?

Thanks!

brianbl

The issue for the DW is the IDs for the products.

If the migration of the 6 catalogs into 1 catalog does not change the
product ids, your historical data should continue to be valid. However, if
the ids in the combined catalog are different from the ids in the 6
catalogs, then your historical data will not be valid.

Rebuilding the DW is the surest way to insure the data integrity, but you
need all of the historic data for that.

I don't have the 2002 reports in front of me, but any report with products
in them would be affected since it's product IDs that might change.

If you're going to reimport the data, you don't have to worry about
updating any of the DW tables. They'll be consistent with the reimport.
The tables that hold Catalog data are:

Products
CatHierarchy
Category
CatalogGlobal

But the catalog import task has a lot of special processing to insure that
these tables have consistent data, so I would not recommend writing scripts
to process them.

--------------------
From: "mzzm" <markmccrimmon@hotmail.com>
Newsgroups:
microsoft.public.commerceserver.catalog,microsoft. public.commerceserver.data
warehousing
Subject: Impact of Catalog changes on an existing CS Data Warehouse?
Date: 15 Feb 2005 20:05:01 -0800
Organization: http://groups.google.com
Lines: 27
Message-ID: <1108525496.218321.313140@c13g2000cwb.googlegroups .com>
NNTP-Posting-Host: 64.53.233.132
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1108526706 27443 127.0.0.1 (16 Feb 2005
04:05:06 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 16 Feb 2005 04:05:06 +0000 (UTC)
User-Agent: G2/0.2
Complaints-To: groups-abuse@google.com
Injection-Info: c13g2000cwb.googlegroups.com; posting-host=64.53.233.132;
posting-account=5uxQ2QwAAABmVisMEF-U-Z6h4-hF30A0
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED02.phx.gbl!tornad o.fastwebnet.it!tiscali!ne
wsfeed1.ip.tiscali.net!news.glorb.com!postnews.goo gle.com!c13g2000cwb.google
groups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.commerceserver.datawarehousing:38 0
microsoft.public.commerceserver.catalog:782
X-Tomcat-NG: microsoft.public.commerceserver.datawarehousing

CS2002 (SP2 + Feature Pack 1)

I am working with a client that is planning on migrating 6 base
catalogs into one. There will continue to be some virtual catalogs off
of the single base catalog. The concerns are in what happens to the
data warehouse and reports. The site has been collecting data (orders,
products, web logs) for nearly a year and they don't want to lose their
data. All of the products will continue to reside in the new base
catalog and the previous base catalogs will simply be the top level
category in the new base catalog.

Questions:

What happens to the current data warehouse? Can I simply rebuild the
entire data warehouse?

What happens to the reports? Which stock reports are affected?

What should I be concerned with in the migration of data?

What tables do I need to manually write SQL scripts for in order to
update from the previous to the new catalog?

What steps should I follow?

Thanks!

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team