If you have another drive i guess it wouldn't hurt, I think the best practice is to cycle it regulary and setup alerts that will let you know...

What did you end up setting the key for LEA_CODE ?

The duplicates that you are experiencing are normal as the key is now different for each of the values...

You should be able to do this if you use an expression over creating a sql statement with parameters.

though i agree with the others this is not the best approach...

Performace Guard (Shehap) (10/11/2011)

---

In order to save current Emergency situation , you have to follow up the next steps by the same order:

1.Switch DB into Simple mode ..and wait for...

Is the LEA_CODE unique across the whole table..

as in does

SELECT LEA_CODE , COUNT(*)

FROM Dim_School

group by LEA_CODE

having COUNT(*)...

the hierachies will still work without attribute relationships but the perfromance would not be optimal.

I would suggest setting them up, but do them one at a time starting from the...

Debbie Edwards (10/11/2011)

---

It just got worse. I deleted the dimesnion and recreated and then processed and now its failing based

on where SCH_DFEE= '3805'

the school DFES is used within 3 LEAs...

Debbie Edwards (10/11/2011)

---

Its certainly a lot more difficult to set up that I first thought.

I need to have a good old think about the hierarchy

Primary Phase has LEA code of...

This is quite common, the best advice i can give would be to remove all your attribute relations for the hierachy , it will complain that it is inefficent...

if you have a unqiue code for each row then you should be fine,

I assume that you have a User Defined Hierachy setup?

If so, could you check how the attibute...

to check for duplicates query your source table where LEA_CODE = 885.

By definition an attribute Key has to be unique otherwise SSAS will not know what value to use when...

Check that you do not have a duplicate in your source table for

LEA_CODE = 885

and if you dont, then check that the attribute relationships for the attribute LEA_CODE are setup...

check the log of the server and this will give you the error code and from that you can work out why you cant login. eg. bad password, ...

have you tried removing the multi-part column identifiers from the insert statement?

eg

TGT.INSTALL_ID

to

INSTALL_ID

you dont need to select any of the columns since you are after a row-count, so un-tick them.. and try again