Home Forums SQL Server 2005 SQL Server 2005 Strategies Brainstorming on strategies for a database with some data warehouse characteristics but with some updating required RE: Brainstorming on strategies for a database with some data warehouse characteristics but with some updating required

  • Can you please elaborate on this? I have not worked with data warehouses so am only somewhat familiar with how they work. What I am envisioning (with no idea of the feasibility) is to only house the static data in the data warehouse, not the fields and tables that users can modify. I wouldn't think that a solely DW solution would work because of the need to update. Is it possible to join across the two? Or to query the DW, populate a temp table with a list of IDs that it returned and join that in the SQL? Having never queried a DW I don't know how similarly that works, whether you can query from .NET etc.

    One of the storage mechanisms when creating cubes in DW is called ROLAP, relational olap and if my memory serves me correctly, it can be used with the base database and updates happen on the fly against the static fields. Other mechanisms would be MOLAP and HOLAP, probably you could find some more details of msdn.

    Thanks for the ideas![/quote]