Hi There, i would put it all in one fact table too, i'd consider clustering / partitioning it the other way though, i.e. DateKey, CustomerKey.

If most of the data warehouse...

there are loads of ways to achieve this..

How many rows of data are we talking about in the tables? if we're talking a few thousand and you are able to...

Essentially you're looking for the best way to find records that have changed in your source system?

If your source system is a SQL Server 2012 enterprise you could look into...

Hi Brian,

Thanks for replying. I have found a few articles that refer to ownership chaining but haven't been able to find anything specific enough to my problem to help...

thats great, exactly what i wanted thanks very much.

sorry i should of been more specific....

i mean that i want to be able to write code in the ssis package that works out if it is currently being executed...

Yes i would like to know this too!

Hi thanks for replying, the mart is more complex than that there are 6 other fact tables, 25 other dimensions, i've cut it down just to show whats relevent for...

this might sound silly but try adding 3 semi colons to the end of the file name string (";;;")

Hi olga, thanks, that is useful, it gives me some confidence in my idea and some very useful tips, can you recommend any resource where i can read though some...

don't take this the wrong way, the new design is kind of why i posted this topic.

I'm by no means an expert, but i'm fairly well experienced with data warehouses...

hi loner, thanks for taking an interest..

currently at 3 fact tables and about 25 dimensions...

the bottle neck comes from the data warehouse being so abstract and the OLTP source being...