I have a parent table with a column I want to drive partitioning off,
but the child tables, as you can guess don't have that same
information in them, hence a normalized database :).  Is there an
approach to add the same criteria for child tables in the same

 In the SSAS tutorial online Lesson 4, I am not sure what is the major
purpose of creating a "new attribute relationship" in "Dimension Structure
--> Hierarchies and levels"?  I understand it is for the sorting purpose if
creating a "new attribute relationship" in the Attributes ...

I have a question about use of many-to-many dimensions. There is a
huge fact table joined to a dimension, and that dimension has a
factless many-to-many table with attributes attached. Question: when
attribues of a dimension record which has been used in the fact table

I am designing a dimBroker table about all the Borker information.  However,
there is a table called BrokerContact in the OLTP systems.  Obviously, one
broker can have multiple contacts.  What is the best way to design the
relationship in the Dimension Model?  Should I make it a ...

Scenario is as follows:
There is an operational data store, which holds customer related data.
In order to provide analytical view, data is fed into the data
warehouse, where statistics are calculated.

Looking at M$ and Kimball examples - I don't see any of them defining a PK
inside the fact tables.  Isn't this bad since it won't offer integrity and
allow duplicates to be inserted?

I found this thread about whether to update fact tables in data
warehouses, other than for errors in the data.
http://groups.google.com/group/microsoft.public.sqlserver ...

I'm curious about theory of cross table references.  I understand the need
but I'm wondering best practices.  Specifically, should Cross-tables only be
made up of foreign keys or is it possible to have other columns?
For example, would this be an acceptable solution.

I'm a beginner at DW and BI. I'm posting to this NG because my current
(and first) data warehouse project is using SQL Server 2005 and my
question is regarding the Kimball book "The Microsoft Data Warehouse
Toolkit" (2006).

I dont know if im in the right group.  My scenario is like this.  Transaction logs are eating up my server's hard drive. Almost 60% of my space is transaction log.  What are these? Can I simply delete it? Can I compress this?  Can someone explain this log file.
Thank you in ...

I'm using AS 2005, I'm trying to create a cube using the wizard and AS
2005 is detecting my Dimension tables as being fact tables and when I
try to switch them to Dim table, it will not let me go further. Does
anyone know how to get through this? These are reference tables and

I have the following:
A hierarchy named [Tire].[Tire Hierarchy] that contains a list of tires by
tire manufacturer.
I have two measures in the fact table:

I have a table that I am converting to a cube with almost 1 million rows in
it. I am curious if in the dimension table, is it good design to have a 1:1
relationship with the fact table rows, or should I distinct the data in the
dimension table, and point to it from the fact ...

I'm looking at replicating data from our OLTP database to a separate
SQL server for purposes of reporting on.
It needs to be real-time so i'm trying to use transactional
replication.