Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Reporting Database and OLAP combined? Expand / Collapse
Author
Message
Posted Wednesday, February 5, 2014 8:08 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, February 7, 2014 11:44 AM
Points: 52, Visits: 210
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
Post #1538199
Posted Wednesday, February 5, 2014 10:47 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:58 PM
Points: 6,172, Visits: 7,246
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
Post #1538291
Posted Wednesday, February 5, 2014 6:32 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, February 7, 2014 11:44 AM
Points: 52, Visits: 210
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...
Post #1538441
Posted Wednesday, February 5, 2014 10:06 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:58 PM
Points: 6,172, Visits: 7,246
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
Post #1538463
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse