InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 17:49:39 GMT20http://www.sqlservercentral.com/Forums/Topic1354246-17-1.aspx[quote][b]Thomas LeBlanc (9/5/2012)[/b][hr]I would first suggest reading some articles from the Kimbal group and concentrate on Fact tables - Tranaction, Snapshot and Accumalitve. You need this understanding to get the measures the reports are requiring.http://www.kimballgroup.com/[/quote]Making it easier for those that will follow:[b][url]http://www.kimballgroup.com/[/url][/b]Wed, 05 Sep 2012 09:37:32 GMTLynn Pettishttp://www.sqlservercentral.com/Forums/Topic1354246-17-1.aspxI would first suggest reading some articles from the Kimbal group and concentrate on Fact tables - Tranaction, Snapshot and Accumalitve. You need this understanding to get the measures the reports are requiring.http://www.kimballgroup.com/Wed, 05 Sep 2012 09:07:30 GMTThomas LeBlanchttp://www.sqlservercentral.com/Forums/Topic1354246-17-1.aspx[quote][b]Evil Kraig F (9/4/2012)[/b][hr]For warehouses, particulary for cubes, you need to start with 'what questions do I want to ask of the data?' This will help inform you of what are facts and what are dimensions. Incredibly short form: Facts can answer questions, Dimensions will describe facts.In this case, it looks like you want to ask questions about the projects, so think of that as your fact table, and decide what questions you want to be able to ask of it, and then hang your dimensions off the resulting fact table.[/quote]In all honesty none of the OLTP tables/data you are describing really translates into a Fact table as it stands. Agree with EKF - what are your questions? What do you want your reports to tell you?Your fact table(s) generally represent the 'transactional' element of your system. So, for example, if I rent cars, my dimensions might be my cars, customers, rental stations (and never forgetting date) but the transactional element is the process; the actual renting of the car. So my fact table would bring together a customer, a car, a rental station and a date together with the relevant bits of data (the 'measures') like the cost and the duration of the rental. The Dimensions are the objects and the Facts are the processes.There are some great free resources on the Kimball website that may help you get moving [url=http://www.kimballgroup.com/data-warehouse-and-business-intelligence-resources/kimball-core-concepts/]http://www.kimballgroup.com/data-warehouse-and-business-intelligence-resources/kimball-core-concepts/[/url]Tue, 04 Sep 2012 19:10:02 GMTMissTippsInOzhttp://www.sqlservercentral.com/Forums/Topic1354246-17-1.aspxFor warehouses, particulary for cubes, you need to start with 'what questions do I want to ask of the data?' This will help inform you of what are facts and what are dimensions. Incredibly short form: Facts can answer questions, Dimensions will describe facts.In this case, it looks like you want to ask questions about the projects, so think of that as your fact table, and decide what questions you want to be able to ask of it, and then hang your dimensions off the resulting fact table.This of course is not the only approach to warehouse building, but it's an excellent starting point if you're new to the process. Then take what you've learned and re-read all that material that's got you twisted around and it should make a TON more sense.I know it's not what you're asking for, you're looking for a solution. I'm loathe to give you *my* solution because I doubt the questions I'd expect to ask of data are the ones that are actually on your mind.Tue, 04 Sep 2012 17:02:53 GMTEvil Kraig Fhttp://www.sqlservercentral.com/Forums/Topic1354246-17-1.aspxHi all,I have an OLTP Database and we are currently planning to build a datawarehouse and a cube and then reports over the cube. I am totally new to OLAP. Please help me figure out the solution by explaining the below question.I have 5 tables in my OLTP.User(id, login, fname, lname)Proj(id, name, desc, website)members(id, user_id, project_id)roles(id, name)member_roles(id, member_id, role_id)Now, I have to figure out Dimensions and Facts from these tables (STAR SCHEMA). I am a newbie to this total terminology.From my readings I figured out, that I will need,DimProj(ProjectKey, Pid, name, desc, website)DimRole(RoleKey, Rid, name)DimUser(UserKey, UID, login, fname, lname)Fact_MemberRoles(MemberRoleKey, UserID, RoleID, ProjID)Is this correct?? Please correct and show me a way to move ahead.ThanksTue, 04 Sep 2012 16:44:40 GMTa4apple