Hi!

I am using the SQL Server 2005 platform.

I have an SSAS project in Visual Studio (or is it BI Studio) that contains 3
cubes and a number of dimensions. Some of the dimensions are shared between
the cubes, but not all. I have two data source views, each containg a fact
table.

I have for instance 2 product dimensions that are not shared and I am
getting confused when having all this in one project as I don't see which
dimensions belong to which cube.

I considered renaming the dimensions, but that doesn't work out for the
shared.

I now consider to create one SSAS project for each cube. Is that bad design
or is it a sensible approach to my challenge?

Also: In the database I now have a lot of dimension tables and it is hard to
see which fact table these belong to. Do I violate good design if I put
tables related to one cube in it own schema in the data warehouse database?

I organize my AS2005 projects into datamarts.


"Billy" <Billy (AT) discussions (DOT) microsoft.com> wrote

How does a datamart differ from a data warehouse?

Is a datamart a fact cube and its tables stored in its own schema in SQl
Server 2005?

I would be very pleased if you could write a little more in detail how your
approach is.

Thanks in advance!

"Jesse O" wrote:

In theory, datamart is just a single subject area or business process. Data
warehouse may consist of more than one datamart for business integrations.

Whether a datamart should be configured by a fact cube, this is a design
issue.

"Billy" wrote: