Using Non BI database as source to Build SSAS cubes and SSRS reports .

hi,
I have a requirement where I have to use existing database(OLTP) as my source to the SSAS cubes and then to build the reports.
Where for Cubes and Reports I uses SQL Server BI edition. But my existing source data will be in non BI database.
My questions are
1) Can I create Fact and Dimension Model in Non BI Db and connect the same to SSAS and SSRS? What you suggest?
2) Can I use cubes and reports without modifying the existing OLTP DB structure to fact and Dimension? 
Thanks
Naveen

hi,
I have a requirement where I have to use existing database(OLTP) as my source to the SSAS cubes and then to build the reports.
Where for Cubes and Reports I uses SQL Server BI edition. But my existing source data will be in non BI database.
My questions are
1) Can I create Fact and Dimension Model in Non BI Db and connect the same to SSAS and SSRS? What you suggest?
2) Can I use cubes and reports without modifying the existing OLTP DB structure to fact and Dimension? 
Thanks
Naveen
1. Yes. you can
It doesnt necessary need to set up a OLAP system. However making design inline with OLAP would be easier to implement in SSAS
2. Again yes
But using OLTP designed tables in SSAS/SSRS would require some additional overheads at querying level like referenced lookups in SSAS vs lots of joins in backend queries in SSRS.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

  • How to use non-MySQL database with DW and PHP...???

    I need to connect to a data-source that is not MySQL from
    with my PHP scripts. The only option I get under the Databases tab
    in the Application panel is MySQL Connection. What about just
    standard ODBC connections? Will DW not handle those for me? Do I
    have to do all of that by hand??
    Any information would be greatly appreciated. Thanks!

    "Angell EYE" <[email protected]> wrote in
    message
    news:fc4eaj$fmn$[email protected]..
    >I need to connect to a data-source that is not MySQL from
    with my PHP
    >scripts.
    > The only option I get under the Databases tab in the
    Application panel is
    > MySQL
    > Connection. What about just standard ODBC connections?
    Will DW not
    > handle
    > those for me? Do I have to do all of that by hand??
    >
    > Any information would be greatly appreciated. Thanks!
    There once existed an opensource servermodel called phakt
    that used the
    ADODB database abstraction library,
    the company that created and supported it was bought by Adobe
    and
    subsequently the project was cancelled.
    A group of people (including me) started a community
    initiative@
    http://openphakt.sourceforge.net
    to continue distribution and development of
    phakt, but unfortunately I don't have access to Dreamweaver
    CS3 due to lack
    of funding.
    Phakt will almost certainly NOT run on CS3 in it's current
    state, but is
    should support previous versions.
    Joris

  • Source Control 3.1 : History and change reports

    Robo Source Control 3.1 : History and change reports are allways empty. I only see titles on the file report.htm (using IE9 or Google Chrome).

    What I was saying in your other post was not necessarily that it will work differently on a 64 bit machine, simply that there were known issues with a 64 bit machine that are referenced in
    http://blogs.adobe.com/techcomm/2011/12/robohelp-9-0-2-is-now-available.html
    It may be the fix referred to there is simply to make it work the same way as on a 32 bit machine and clearly that is giving you grief. Only way way to find out.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • [Forum FAQ] How to use parameter to control the Expand/Collapse drill-down options in SSRS report?

    In SQL Server Reporting Services (SSRS), drill-down is an action we can apply to any report item to hide and show other report items. They all are ways that we can organize and display data to help our users understand our report better. In this article,
    we are talking about how to use parameter to control the Expand/Collapse drill-down options in SSRS report.
    Consider that the report has a dataset (dsSales) with following fields: SalesTerritoryGroup, SalesTerritoryCountry, CalendarYear, SalesAmount.
    1. The report has the following group settings:
    Parent Group: SalesTerritoryGroup
     Child Group: SalesTerritoryCountry
      Child Group: CalendarYear
       Details: SalesAmount
    2. Add three parameters in the report:
    GroupExpand:
    Available Values: “Specify values”
    Label: Yes           Value: Yes
    Label: No            Value: No
    Default Values: “Specify values”
    Value: Yes
    CountryExpand:
    Available Values: “Specify values”
    Label: Yes           Value: =IIF(Parameters!GroupExpand.Value="No",Nothing,"Yes")
    Label: No            Value: No
    Default Values: “Specify values”
    Value: =IIF(Parameters!GroupExpand.Value="No","No","Yes")
    YearExpand:
    Available Values: “Specify values”
    Label: Yes          
    Value: =IIF(Parameters!GroupExpand.Value="No" or Parameters!CountryExpand.Value="No",Nothing,"Yes")
    Label: No            Value: No
    Default Values: “Specify values”
    Value: =IIF(Parameters!GroupExpand.Value="No" or Parameters!CountryExpand.Value="No","No","Yes")
    3. Right click SalesTerritoryCountry icon in the Row Groups dialog box, select Group Properties.
    4. Click Visibility in the left pane. Select “Show or hide based on an expression” and type with following expression:
    =IIF(Parameters!GroupExpand.Value="Yes", False, True)
    Select “Display can be toggled by this report item” option, and select “SalesTerritoryGroup” in the drop down list.
    5. Use the same method setting CalendarYear, (Details) drill-down with following expression:
    =IIF(Parameters!CountryExpand.Value="Yes", False, True)
    =IIF(Parameters!YearExpand.Value="Yes", False, True)
    6. Click SalesTerritoryGroup text box in the tablix. Select InitialToggleState property in the Properties dialog box, and type following expression:
    =IIF(Parameters!GroupExpand.Value="Yes", True, False)
    7. Use the same method setting SalesTerritoryCountry, CalendarYear text box with following expression:
    =IIF(Parameters!CountryExpand.Value="Yes", True, False)
    =IIF(Parameters!YearExpand.Value="Yes", True, False)
    After that, when we preview the report, we can use these three parameters to expand/collapse drill-down.
    Note:
    In our test, we may meet following issue. We can check the expression of InitialToggleState property to troubleshooting the issue.
    Applies to
    Reporting Services 2008
    Reporting Services 2008 R2
    Reporting Services 2012

    In SQL Server Reporting Services (SSRS), drill-down is an action we can apply to any report item to hide and show other report items. They all are ways that we can organize and display data to help our users understand our report better. In this article,
    we are talking about how to use parameter to control the Expand/Collapse drill-down options in SSRS report.
    Consider that the report has a dataset (dsSales) with following fields: SalesTerritoryGroup, SalesTerritoryCountry, CalendarYear, SalesAmount.
    1. The report has the following group settings:
    Parent Group: SalesTerritoryGroup
     Child Group: SalesTerritoryCountry
      Child Group: CalendarYear
       Details: SalesAmount
    2. Add three parameters in the report:
    GroupExpand:
    Available Values: “Specify values”
    Label: Yes           Value: Yes
    Label: No            Value: No
    Default Values: “Specify values”
    Value: Yes
    CountryExpand:
    Available Values: “Specify values”
    Label: Yes           Value: =IIF(Parameters!GroupExpand.Value="No",Nothing,"Yes")
    Label: No            Value: No
    Default Values: “Specify values”
    Value: =IIF(Parameters!GroupExpand.Value="No","No","Yes")
    YearExpand:
    Available Values: “Specify values”
    Label: Yes          
    Value: =IIF(Parameters!GroupExpand.Value="No" or Parameters!CountryExpand.Value="No",Nothing,"Yes")
    Label: No            Value: No
    Default Values: “Specify values”
    Value: =IIF(Parameters!GroupExpand.Value="No" or Parameters!CountryExpand.Value="No","No","Yes")
    3. Right click SalesTerritoryCountry icon in the Row Groups dialog box, select Group Properties.
    4. Click Visibility in the left pane. Select “Show or hide based on an expression” and type with following expression:
    =IIF(Parameters!GroupExpand.Value="Yes", False, True)
    Select “Display can be toggled by this report item” option, and select “SalesTerritoryGroup” in the drop down list.
    5. Use the same method setting CalendarYear, (Details) drill-down with following expression:
    =IIF(Parameters!CountryExpand.Value="Yes", False, True)
    =IIF(Parameters!YearExpand.Value="Yes", False, True)
    6. Click SalesTerritoryGroup text box in the tablix. Select InitialToggleState property in the Properties dialog box, and type following expression:
    =IIF(Parameters!GroupExpand.Value="Yes", True, False)
    7. Use the same method setting SalesTerritoryCountry, CalendarYear text box with following expression:
    =IIF(Parameters!CountryExpand.Value="Yes", True, False)
    =IIF(Parameters!YearExpand.Value="Yes", True, False)
    After that, when we preview the report, we can use these three parameters to expand/collapse drill-down.
    Note:
    In our test, we may meet following issue. We can check the expression of InitialToggleState property to troubleshooting the issue.
    Applies to
    Reporting Services 2008
    Reporting Services 2008 R2
    Reporting Services 2012

  • Hidden Database Items - Using Non-database Items

    I am making my first form. It is based on a table having three columns, two are IDs (primary keys) for other tables ( org_organization_definitions and po_vendors ), and one is an enabled_flag containing either Y or N. In my form I need to hide the IDs of the underlying table, but display the organization_code and vendor_name from the IDs of the records from their respective home tables, and be able to query records by organization_code and vendor_name.
    I have tried two methods:
    In the first I created a block from the table with the ID and enabled_flag columns, and manually created text items for organization_code and vendor_name that are not database items and manually fill them in the post-query trigger of the block. The problem I ran into with this method was that I did not know how to use the manual text items for searching, and I could not get the LOVs to behave as expected as with database items.
    In the second method, I created a view with all of the data that I needed to display, and based the block on that. Of course I cannot update or insert into the view, so I wanted to handle the updates and inserts manually with my own DML statements. With this method I have two problems, I don’t know how to bypass the form runtime not wanting to let me update values, and once I do, I am not sure how to manually go through each record to check to see if it has been changed or not.
    I am not sure if either of my methods are the only two options or the best ways. Any help you can provide me with in this matter is appreciated.
    Thank You,
    Ryan

    hi,
    I have a requirement where I have to use existing database(OLTP) as my source to the SSAS cubes and then to build the reports.
    Where for Cubes and Reports I uses SQL Server BI edition. But my existing source data will be in non BI database.
    My questions are
    1) Can I create Fact and Dimension Model in Non BI Db and connect the same to SSAS and SSRS? What you suggest?
    2) Can I use cubes and reports without modifying the existing OLTP DB structure to fact and Dimension? 
    Thanks
    Naveen
    1. Yes. you can
    It doesnt necessary need to set up a OLAP system. However making design inline with OLAP would be easier to implement in SSAS
    2. Again yes
    But using OLTP designed tables in SSAS/SSRS would require some additional overheads at querying level like referenced lookups in SSAS vs lots of joins in backend queries in SSRS.
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Using Non cumulative key figure in Real time cube

    Hi gurus,
    I have used non cumulative key figure in a real time cube and when i tried to enter some data using RSINPUT ,it is giving an error and the data is not getting saved.
    Can anyone please tell me how to use the Non cumulative key figure in the Real time cube .
    Thanks in advance
    Regards,
    Ravikanth

    Hi Ravi,
          Please make sure that when you use a non cumulative key figure iun your real time info cube, then choose a time reference characteristic for that key figure.
    Then, this time reference characteristic applies for all the non-cumulative values of the InfoCube and must be the u201Csmallestu201D of the time characteristics present in the InfoCube.
    For more detaisl, refer to the [http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm]
    Thanks & Regards,
    Balajee.

  • GLOBAL VARIABLES FOR NON-ORACLE DATABASE

    What is the alternative of global variables in Form 5.0 when using non-oracle databases. I know one way is passing parameters, is there any other way? I have few variables which need to be global in my application.
    Thank you
    null

    There is no other way.. you have to use either Global variables or parameter lists to pass values from one form to another form.. With in the form you can always use null canvas item to store and pass values in different program units or triggers..
    have a nice day
    Suresh

  • Global user in non-oracle database

    What is the alternative of global variables in Form 5.0 when using non-oracle databases. I know one way is passing parameters, is there any other way? I have few variables which need to be global in my application.
    Thank you
    null

    There is no other way.. you have to use either Global variables or parameter lists to pass values from one form to another form.. With in the form you can always use null canvas item to store and pass values in different program units or triggers..
    have a nice day
    Suresh

  • SSAS Tabular - rows in model that are NOT in source -due to building of "cube"?

    I have a source SQL table that is basically a SELECT * FROM SQLSOURCETABLE for a table in a TABULAR model.
    When that table processes, it appears to not only return just the rows in the table, but to build a cube and store results for rows that do not exist.
    That is to say:
    SalesAmount
    SalesCategory
    SalesYear
    The table has rows for SalesCategory="Bikes" and SalesYear=2012.
    However the source SQL table has no Bike sales in the year 2013.  So instead of the tabular model having no rows for 2013 it instead has SalesCategory: Bikes, SalesYear:2013 and SalesAmount = 0
    Querying the SQL source table with:
    SELECT SalesAmount,SalesCategory,SalesYear
    FROM SQLSOURCETABLE
    WHERE SalesCategory='Bikes' AND SalesYear=2013
    would return zero rows.  However, in the tabular model after processing it does return rows, with SalesAmount=0.
    I assume this is standard behavior for Tabular models (since they are part of SSAS and well... just building their cube?)
    I guess I just never thought of it building out data for intersections that did NOT exist, only for intersections of data that DID exist?
    *EDITED: Fixed typo I had 2014 instead of 2013 for year

    Hi ,
    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Is it proper to use indexed views as the source of your cubes

    I understand that you're supposed to use views as the source of your SSAS cube because it provides a layer of abstraction and allows you to make schema changes without adversely effecting the cube. I also know that when you have users accessing the warehouse
    you should use indexed views. However I just ran across this little gem:
    "With schema binding, if the base object is bound to another object, you will not be able to modify the base object unless you drop or alter the object to remove the schema binding."
    That seems to run contrary to the goal of abstraction, that is, if I'm reading that correctly. What am I missing?

    You should use schema bound / indexed views very little.  They have high overhead associated with them.
    In order to change a base table referenced by a schema bound view, you must drop the view, make the change to the table and recreate the view (and any indexes).  Depending on the change to the base table this may or may not have any affect on the view. 
    This is by design.

  • Anyone using non Apple ram with standard heatspreaders?

    Hi,
    Is anyone using non standard Apple ram with normal sized heatsink/heatspreaders and if so have you had any problems?
    I can find ram for the same spec that works but they only have the standard thin silver heatspreader attached and am concerned about running temps etc.
    If anyones using these modules without problems, please post here!
    Thanks.

    Might want to read this article and it has some good information to help you decide.

  • I see 'enq: JI - contention' when building multiple cubes/partitions

    Version 11.2.0.3
    I can successfully build multiple partitions of a cube simultaneously by supplying the degree of parallelism that I want. I can also build multiple cubes and multiple partitions of multiple cubes by submitting separate jobs (one per cube) with parallelism set in the job (for number of partitions per job/cube).
    My goal was to refresh 2 cubes simultaneously, 2 partitions in parallel each, so that 4 partitions total were refreshing simultaneously. There were sufficient hardware resources (memory and processes) to do this. I tried to submit 2 jobs, one for each cube, with parallel 2 on each.
    What happens is that 3 partitions start loading, not 4. The smaller of the 2 cubes loads 2 partitions at a time, but the larger of the cubes starts loading only 1 partition and the other partition process waits with JI - contention.
    I understand that JI contention is related one materialized view refresh blocking another refresh of the same MV. Yet simultaneous refresh of different partitions is supported for cube MVs.
    Because I see the large cube having the problem but not the smaller one, I wonder if adding more hash partitions to the AW$ (analytic workspace) table would allow more concurrent update processes. We have a high enough setting for processes and job_queue_processes, and enough available threads, etc.
    Will more hash subpartitions on the AW$ table allow for more concurrency for cube refreshes?

    It looks like the JI contention was coming from having multiple jobs submitted to update the SAME cube (albeit different partitions). Multiple jobs for different cubes (up to one job/cube each) seems to avoid this issue. I thought there was only one job per cube, but that was not true.
    Still, if someone has some insight into creating more AW hash subpartitions, I'd like to hear it. I know how to do it, but I am not sure what the impact will be on load or solve times. I have read a few sources online indicating that it is a good idea to have as many subpartitions as logical cube partitions, and that it is a good idea to set the subpartition number to a power of two to ensure good balance.

  • Using FORMAT_STRING from SSAS cube - not working consistently

    Here's the deal.  
    I've got an SSAS cube and I am scoping the format of the measures based on dimension members. 
    Like this.
    scope(( [Account].[Level 5].&[I000900000] )); 
    format_string(This) = "(#,0,);#,0,";   
    end scope; 
    I'm then calling this format in the SSRS report using typical SSRS trickery and hacks.  
    Well. When I run the report for one date (this is a GL financial cube), this works perfectly.  When I run the report for a different date, it all of a sudden doesn't work.  When I view the data in excel through a pivot table, everything is fine.
    It's driving me crazy.  Has anyone else experienced something like this.

    Hi Baracus,
    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Constraints need to consider to build Inventory CUBE in ECC 6.0

    Hi,
    I am new to ECC. Can any one help me on
    what are all the details (or) required constraints need to consider , to generate inventory cube?
    If my Manager asked me to generate INVENTORY CUBE.What questions can i shoot to my manager.
    Early Responce is Ariciated.
    Thanks in Advance.
    ~bharath

    Inventory Cube : 0IC_C03  
    Suggest you to explore with above search to get more details. would like to share below links for your ready reference.
    http://wiki.sdn.sap.com/wiki/display/BI/StepbyStepLoadingDatatoInventory+Cube
    http://help.sap.com/saphelp_nw04/helpdata/EN/5b/8dc73cee4fb55be10000000a114084/content.htm
    Once you search on the forum, you will observed constraints / issues faced by consultant on building inventory cube and sdn experts would have suggested ways to resolve it.
    all the best.

  • Using Pivot-Slicers on a SSAS Cube with Access Rights

    Dear all,
    we're using a SSAS Cube and try to access the data by an Excel Pivot. That works fine.
    Furthermore, we are using the slicer feature of Excel 2010 to select the specified data.
    The problem is that we have a dedicated rights concept and only some users are allowed to see all dimension elements. Other users are not allowed to see all the data. This is ok and works for Pivots, as we can see there only the elements which the respective
    user is allowed to see. In the case of slicers this doesn't work: the slicers always show all dimension elements (the restricted ones with 0-values). Can this somehow be repaired, so that the user only sees the elements in the slicer he's allowed to see?
    Best Regards
    Bjoern

    Hi Charlie,
    I guess we have some kind of language barrier here because i did not fully understand your explanation.
    I've got a User Günther who is only to allowed to see the revenues of his own company.
    Therefore, he has got a restriction on the company-dimension, which has 100 companies. He is only allowed on his own company.
    If we open a new pivot with the company dimension, he will only see 1 column (with his company) instead of 100.
    If I currently add a slicer to the pivot, the list of elements in the slicer contains 100 companies. All of them are also shaded (which shows, that data is available). If i click on a shaded company, on which he is not allowed, Günther only sees zero-values
    (0,00).
    In this case, it would be better to only see the 1 company the slicer shaded, which has values that Günther is allowed to see. Then, he would only see his own company shaded and 99 would have the look like being "without data". 
    If my proposal would be impleneted, it would be much easier to use excel BI services on a big SSAS cube with multiple dimensions and multiple users that have different access rights. 
    The best would be, if a slicer could be customized in more details (e.g., with a mdx query).
    // Do I perhaps have misplaced the question into the wrong forum?
    Best Regards
    Bjoern

Maybe you are looking for