Developing ETLs

  • Hello!

    I am new to analysis services and ETL using SQL server 2005, but not SQL Server or databases in general. I have a few questions regarding some data warehousing techniques.

    I have two SQL servers -- one a production and another a test for reporting and analysis services.

    Basically I want to create cubes of data on the reporting server. I have a few dimensions on my live server --

    employees 

    customers

    location ( this is the location where the employee is working)

    sales ( a transactional table)

    ...and more tables that I do not need in the DB

    First --

    I want to create a table on the reporting server which will calculate values based upon employee sales. An example might be:

    EmployeeID     CustomerID    boolContactedCustomer   dtContactedCustomer

    I want this data to be used in a report with the ability to drill down and get more information about the employee or the customer using Microsoft's Analysis services.

    Looking at the theory behind it -- is it best to create ETLs to move all of the tables I need over and then have an ETL calculate the reporting table? Just looking to fill in some cracks here.

    Thanks.

  • This was removed by the editor as SPAM

  • It does not matter if you are using SQL Server 2000 or SQL Server 2005, you can build the dimension tables and fact tables in SQL Server. The analysis service will build the cube for you, but you don't need to use it. You can build the report using reporting service by using SQL Server fact tables.

  • If you use regular SQL server to build the data warehouse, you just build it in star schema. Many company uses RDBMS to build the data warehouse.

  • Thank you!

    I've learned a lot about this over the past few days and I appreciate the feedback.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply