Also, datawarehouses, or more precisely, dimensional models are meant to solve aggregation requirements. OLTP requirements are far more complex. Not all database requirements can be met by the...

Dimensional Models, particularly the SCDs) do not track more than one dimension of time per entity. This is the value of temporal relational modeling. Dimensional systems are typically...

@sqlserver tweeted live in 10 minutes......12 minutes ago...

Change Data Capture and Change Tracking are useful for auditing, but these features are not the same thing as 'temporal modeling'. Among other things, they have no support for valid...

I would strongly advise "against" using history or audit tables for several reasons. You will encounter performance issues, as well as complicate your ability to query your data. ...

You may want to take a look at Microsoft Project REAL.

http://technet.microsoft.com/en-us/library/cc966416.aspx

You could add something like an ExecutionId to every table in your database. When a row is...

To follow up on the last post. Try the following, where the object_id column contains the object_id from sys.objects for the table being referenced.

IF EXISTS (SELECT * FROM...

Lynn,

We already have experience accomplishing answers to these questions. This post of more about inviting the participation of others to tell us about their experiences. Memebers of Adama Systems...

If you wanted to eventually create a stored procedure that would find related requisitions, regardless of which column your target value might be in, would using a UNION statement fulfill...

My apologies for miscommunicating. I'll ask it a different way. How does that recursion not satisfy your requirements?

My question is, what is the significance of having both "AB" and "BA"? I'm assuming from your original post that it is important to allow for that.

CONSTRAINT [PK_Relation] PRIMARY KEY CLUSTERED (requisitionID ASC))

However, for the second PK, it does not violate the key, since "B" is one unique record and "A" is the other, i.e., "BA"...

PRIMARY KEY CLUSTERED (requisitionID ASC, parentRequisitionId ASC))

The PK above means that AB and BA cannot both be records in that table.

The first PK makes a composite of two requisitions unique. So AB and BA are the same record, therefore violating the PK.

George,

In the first part of your post it sounds like you want to implement a simple recursive relationship, i.e., parent-child.

CREATE TABLE [Relation](

requisitionID [int] NOT NULL,

parentRequisitionId [int] NOT NULL,

CONSTRAINT [PK_Relation]

PRIMARY KEY...