3. BI Modeling SQL Server Data Warehouse Source Systems/OLTP Clients Design the Populate Create Query Data Warehouse Data Warehouse OLAP Cubes Data 1 3 4 Query Tools Reporting Analysis 2 Cubes Analysis Services
4.
5. A Logical Cube - Example Product Region West East South North 1999 2000 2001 2002 Milk Donut Sandwich Soda Beer Time $18.00 The Sales$ by Soda by West in Yr of 2001 North South East West Products, Region, Price by 2000 Products, Year, Price in South
6. Analysis Server OLEDB ADOMD .NET AMO IIS TCP HTTP XMLA ADOMD Client Apps BIDS SSMS SSRS Excel Client Server Architecture MOSS
The Work Flow of a Typical Data Warehouse Project Every thing from Data Load to, Cube Design & Deployment and then Reporting can be done by BIDS. BIDS is very powerful and allow to create three types of Project – SSIS, SSAS or SSRS. The data are entered into the OLTP system and then transformed into the Data Warehouse. The transformation occurs with the ETL (Extraction, Transformation, and Load) tool. The current tool with SQL Server 2005 is Integration Services. This initial transformation most often occurs from multiple OLTP source systems to a staging area. The staging area is then used to transform the data. The transform includes the following types of work: Moving data Dealing with invalid data. Surrogate key creation and structuring After the data is in the Data Warehouse it can be queried with any SQL tools and it is ready for OLAP tools as well.
A simple example: A Sales table contain “Product” column, “Region” column, and “Sales $” column. The data are organized by rows. If we turn the relational table into a cube, the Product becomes the Product dimension, the Region becomes Region dimension, and the Sales $ is becomes a measure of the cube.
To find out the how much “Sales $” the “Soda” sold in the “West” region in the year of 2001. We take the intersection of the Soda in the product dimension, the West in the region dimension and the year of 2001 in the Time dimension. This way of thinking will help use MDX (Multiple Dimension Expression) learn faster.
02/10/12 09:30 02/10/12 09:30 AMO -- Analysis Management Objects AMO is the complete library of programmatically accessed objects that enables an application to manage a running instance of Microsoft SQL Server 2005 Analysis Services (SSAS). XMLA (XML for Analysis) Microsoft SQL Server 2005 Analysis Services (SSAS) uses the XML for Analysis (XMLA) protocol to handle all communications between client applications, including SQL Server Management Studio and Business Intelligence Development Studio, and an instance of Analysis Services. To support the discovery and manipulation of data in both multidimensional and tabular formats, XMLA defines two generally accessible methods, Discover and Execute, and a collection of XML elements and data types. Because XML allows for a loosely coupled client and server architecture, both methods handle incoming and outgoing information in XML format. XMLA is optimized for the Internet, where roundtrips to an Analysis Services instance are expensive in terms of time and resources, and where stateful connections to the data limit user connections on the instance. Analysis Services The main executable of Analysis Services is at “C:\\Program Files\\Microsoft SQL Server\\MSSQL.2\\OLAP\\bin\\“ folder. It depends the location you picked at the installation time. The path in your system may different. OLE DB for OLAP Formerly, the separate specification that addressed OLAP extensions to OLE DB. Beginning with OLE DB 2.0, OLAP extensions are incorporated into the OLE DB specification. ADO MD -- ActiveX Data Objects (Multidimensional) A high-level, language-independent set of object-based data access interfaces optimized for multidimensional data applications. Visual Basic and other automation languages use ADO MD as the data access interface to multidimensional data storage. ADO MD is a part of ADO 2.0 and later versions.
Show Example of Adventure Works Cube Creation from backup file using SSMS and then create Analysis Services project by connecting to it using BIDS. Explain what is differences between working with online/offline cubes in BIDS? Purpose of Deploy.
The two major tools used for administration and development are the SQL Server Management Studio (SSMS) and the Business Intelligence Development Studio (BIDS) . The following sections outline each of these tools. SQL Server Management Studio Microsoft SQL Server Management Studio, new in Microsoft SQL Server 2005, is an integrated environment for accessing, configuring, managing, administering, and developing all components of SQL Server. SQL Server Management Studio combines a broad group of graphical tools with a number of rich script editors to provide access to SQL Server to developers and administrators of all skill levels. Business Intelligence Development Studio (BIDS) Business Intelligence Development Studio is Microsoft Visual Studio 2005 with additional project types that are specific to SQL Server 2005 business intelligence. Business Intelligence Development Studio is the primary environment that you will use to develop business solutions that include Analysis Services, Integration Services, and Reporting Services projects. Each project type supplies templates for creating the objects required for business intelligence solutions, and provides a variety of designers, tools, and wizards to work with the objects. Note: Business Intelligence Development Studio, the 32-bit development environment for Analysis Services, Integration Services, and Reporting Services projects, is not designed to run on the Itanium 64-bit architecture and is not installed on Itanium servers. Additionally a series of other tools are installed. Most of these tools are used on a less frequent basis. The following outlines the additional tools (and are either covered in this course or other ProClarity offerings. Ask your instructor).