SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


sql12 tabular mode design


sql12 tabular mode design

Author
Message
skeezwiz
skeezwiz
Mr or Mrs. 500
Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)Mr or Mrs. 500 (502 reputation)

Group: General Forum Members
Points: 502 Visits: 308
Hello, Im finding it a little "extra" work is needed to get a complicated tabular model designed vs traditional OLAP cubes and it also seems more clunky to work with. For example renaming fact/dims tables/columns there is no auto-refresh of the data source view, you have to go to each table properties and refresh there and then modify your affected formulas. Having say 10 facts and 20 dims there are a lot of "inactive" relationships created by the designer which results in custom measures to be created for each of these, why did they do this? E.g. CountofInactiveRelationField:=CALCULATE(COUNT(Table[column]),USERELATIONSHIP(Table[column] ,LookupTable[LookupColumn])). If we dont do this then the counts are not correct for this inactive field. Traditionally to get a simple count rolled up for each dimension there is on standard count measure and the rollup happens automatically in OLAP cube. This happens to be a pain where there are 10+ formulas for each of the facts!

Is this the design experience developers are having out there? or is there some workarounds for this? It seems memory/compression speeds for data loading/retrieve is offset by bad design principles needed to be applied to get it.
tmitchelar
tmitchelar
SSC Veteran
SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)SSC Veteran (251 reputation)

Group: General Forum Members
Points: 251 Visits: 508
Give me a few months and I'll be able to share the frustration! Still waiting on approval for my 2012 Enterprise license. :-D
Samuel Vella
Samuel Vella
SSC Eights!
SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)SSC Eights! (833 reputation)

Group: General Forum Members
Points: 833 Visits: 2144
When working in Tabular mode you need to move away from the concept of fact and dimension tables. Each of those joins will require an index creating on each table which is going to hurt the compression

Denormalising towards a single table will give the best performance and compression

Personally I think the use of the tabular mode should be considered very carefully. It is NOT a replacement for dimensional OLAP. You should not try and store your entire data warehouse in it.

Instead think of it as an easy to setup analytical space for smaller datamarts which you don't want to go to the effort of modelling in the dimensional cube. You can prototype in powerpivot in Excel and then import that model into Visual Studio when you're ready to deploy
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search