Good question ...

The motive was so to avoid having the use dattime comparisisons to identify which version of an entity we used in a decsison making proccess, instead just lay...

I'm currently using the IDENTITY datatype in the Live table its what I use to identify the entity in the live table i.e. PK value...

No 2 versions of the same...

The goal is to version data so I can track changes and identify which versions of an entity were used in decsion making procceses.

Each live table would have 2 keys...

Thanks i'll have a look at this ...

The live/current table will only ever contain one version of the entity as identified using the GID column (PK) ... a supporting Audit table can contain multiple multiple historic versions...

I realise I can use the DTA to analyse the Perm tables i've created I'm just wondering if i've wasted my time here potentially? i.e. could i have just used...

How does the DTA handle Temporary Tables.....

I was of teh opinion that the DTA was incappable of giving suggestions on Temporary tables is that incorrect?

My Perf testing is advancing along i have now removed all indexs and would you believe the DMV's are only suggesting a fraction of the indexes ......

This process is limited...

Firstly these Perm tables are created where before the temp tables were created within the process purely so i could conduct my analysis i.e capture the stats..... I should point...

Thks guys that makes perfect sense

I'll be running this through a staging envoirnment to make sure we don't kill the performance on the system but I appreciate the concern and i couldn't agree with you...

The column list i submitted with this was only as an example, as it turns out the number of columns in this index is quite large at at the very...

Your right in what your saying but as always managers are asking that i reduce the number of users with sysadmin access .... thanks for the reponse I've seen a...

Did this ever work? I'm in the same situation now

This table is a core table i.e. its one...