Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Reporting Database and OLAP combined?


Reporting Database and OLAP combined?

Author
Message
Nick-957131
Nick-957131
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 Visits: 224
I am planning a couple of projects and wondered if I could combine efforts.
We have two specific goals:

1. Reduce load on our OLTP environment by reporting from a dedicated report environment
2. Implement dimensional modeling / cube functionality for analysts

My question is, can I (should I) develop reports over the data source views which will ultimately support the OLAP environment? Currently, I extract data to a staging area and I am in the process of building views which would support dims and facts. Would you suggest building other views over the same staging data to support reporting and / or building reports over the dims / facts or cube itself?

Sorry for the multi-question, fully-loaded, open-ended post. Thanks for your insight.

Nick
Evil Kraig F
Evil Kraig F
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5699 Visits: 7660
I personally wouldn't build views for dims/facts over the staging tables. I'd use SCD2 design and create a proper warehouse. The SSAS then just sits on top of that. You call whichever makes the most sense for the report when you build it.

Running views to make dim/facts only really works for small data loads which you don't need the warehouse for in the first place. The indexing in a warehouse is very different, which is why you reorganize all the data in the first place.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Nick-957131
Nick-957131
Valued Member
Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)Valued Member (54 reputation)

Group: General Forum Members
Points: 54 Visits: 224
Thanks Craig,

I'm a bit new to dimensional modeling and misunderstood a best practice. Rather than using views as source for dims and fact tables... use views of dims and facts to support a cube. This seems to be fairly common with the primary advantage of easy maintenance if you're used to TSQL...

That said... I am working through creation of my dim / facts with intention of building some indexes focused on reads.

I suppose my question now is can I (should I) use the same dim / facts and subsequent views to support reporting as well as ssas?

Thanks again...
Evil Kraig F
Evil Kraig F
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5699 Visits: 7660
Nick-957131 (2/5/2014)

I suppose my question now is can I (should I) use the same dim / facts and subsequent views to support reporting as well as ssas?

Thanks again...

Oh, sure. You'll normally simply preprocess your cubes during overnights for daily work, but if you have reports and the like that don't make sense for the overkill MDX can be sometimes, go nuts.

The reporting database typically won't be real time. If you need real time reports, keep the filters tight and run them off the OLTP system. Warehouses and OLAP are typically used more for overview type stuff, not realtime.

Of course, there's exceptions to that everywhere.


- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
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