April 2, 2012 at 7:51 am
Hi
I've read that if the AttributeHierarchyEnabled property is set to false on attributes, then SSAS will not a build a hierarchy for this attribute although it will still be available as a property of another attribute. This has also the benefit in reducing processing times... well that's what I hoped for! I have a customer dimension and I did disable a number of attributes i.e. by setting the AttributeHierarchyEnabled to false thinking that less SQL statements will be fired to the SQL Server DWH. I was under the impression (or had read it somewhere before) that if the attribute is set to false, then NO SELECT DISTINCT on the attribute column is generated. Well although I disable the attributes, SSAS is still generating these SQL statements and this is slowing down my dimension processing.
Can someone please explain? maybe I'm doing something wrong?
Regards
Brian
Regards
Brian Ellul
----------------------------------------------------------------------------------
Computers are incredibly fast, accurate, and stupid. Human beings are incredibly slow, inaccurate, and brilliant. Together they are powerful beyond imagination.
- Albert Einstein -
April 2, 2012 at 8:41 am
Hi Brian,
I've not performed a trace to disprove this, but it sounds like SSAS is doing what it needs to do - if you want these data items in the dimension, am not sure exactly how SSAS will get that data *without* executing queries against the source.
You could *try* changing the ProcessingGroup on the dimension, from it's default of ByAttribute to ByTable, but be aware, this wil then make SSAS try to load the entire table contents to memory as it processes that dimension - so while you may get fewer queries fired against the source, your server resource usage will likely increase during processing time.
Steve.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply