In this article by Bob Griesemer, author of Oracle Warehouse Builder 11g R2: Getting Started 2011, we will define our cube, which is where our measures will be stored—the facts that users will want to query. There is a wizard available to us for creating a cube that we will make use of to ease our task. So let's start designing the cube with the wizard. We'll create the objects using the wizards that the Warehouse Builder provides for us to simplify the task of building cubes and dimensions.
We will cover:
- Creating a cube with the wizard
- Using the data object editors
Data warehouses are becoming increasingly common as businesses have realized the need to be able to mine the information they have stored in the electronic form in order to provide a valuable insight into the operation of their business and how best to improve it. Organizations need to monitor these processes, define policies, and—at a more strategic level—define the visions and goals that will move the company forward in the future. The Warehouse Builder provides a couple of ways to create a dimension. One way is to use the wizards that it provides, which will automatically create a dimension for us. The other way is to manually create it.
In this article by Bob Griesemer, author of Oracle Warehouse Builder 11g R2: Getting Started 2011, we will create:
- The Product dimension
- The Store dimension
In this article by Bob Griesemer, author of Oracle Warehouse Builder 11g R2: Getting Started 2011, we'll discuss briefly what a Time dimension is, and then we'll dive right into the Warehouse Builder Design Center and create one. A Time dimension is a key part of most data warehouses. It provides the time series information to describe our data. A key feature of data warehouses is being able to analyze data from several time periods and compare results between them. The Time dimension is what provides us the means to retrieve data by time period.Read Oracle Warehouse Builder: Creating the Time Dimension in full
It is not uncommon to run into issues when global security is first enabled in a WebSphere environment. Some of those situations may occur due to performing tasks out of order. Other problematic conditions related to security configuration may take place due to inadvertently omitting one or more steps in a set up process. Moreover, a third category of errors that may happen due to security configuration is caused by using the wrong values to one or more parameters.
In the previous article by Omar Siliceo, author of IBM WebSphere Application Server v7.0 Security, we took a look at tuning websphere security. In this article we will be presented by a set of some conditions that may appear in a WebSphere Application Server ND version 7 (WAS ND7) when global security is first enabled. The first subsection covers circumstances that may come about during the configuration phase. Next, a subsection is included that presents circumstances that may happen at runtime.Read Troubleshooting WebSphere Security-related Issues in full
The generic term "tuning security … " some say, it's an oxymoron. Why so? Well, in many cases, tightening up security is normally reflected in poor performance. So, if a portion of your environment is performing poorly, it may need a review of the security configuration in order to see if loosening it a bit does not compromise the environment itself. This article by Omar Siliceo, author of IBM WebSphere Application Server v7.0 Security, briefly describes tuning in three major areas:
- General security configuration
- CSIv2 connectivity
- LDAP and Web authentication
A Windows Azure hosted service may comprise multiple instances of multiple roles. These instances all run in a remote Windows Azure data center—typically 24*7. The ability to monitor these instances non-intrusively is essential both in detecting failure and in capacity planning. This article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, shows how Windows Azure Diagnostics provides for the non-intrusive capture of diagnostic data and its subsequent persistence to the Windows Azure Storage Service. Windows Azure Diagnostics supports various standard sources, allowing for their extensibility where appropriate. The topics covered in this article include:
- Using the Windows Azure Diagnostics trace listener
- Performing an on-demand transfer
- Implementing custom logging
- Accessing data persisted to Windows Azure Storage
- Using the Windows Azure Platform
- PowerShell cmdlets to configure Windows Azure Diagnostics
A Windows Azure hosted service may comprise multiple instances of multiple roles. These instances all run in a remote Windows Azure data center—typically 24*7. The ability to monitor these instances non-intrusively is essential both in detecting failure and in capacity planning.
However, there are times, especially early in the development process, when non-intrusive diagnostics monitoring is not sufficient. In this article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, we will see the benefits of intrusive monitoring of a Windows Azure role instance using IntelliTrace.Read Using IntelliTrace to Diagnose Problems with a Hosted Service in full
The default configuration for Windows Azure Diagnostics captures some data but does not persist it. Consequently, the diagnostics configuration should be modified at role startup. In this article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, the Initializing the configuration of Windows Azure Diagnostics recipe, shows us how to do this programmatically, which is the normal way to do it. In the Using a configuration file with Windows Azure Diagnostics recipe, we see how to use a configuration file to do this, which is necessary in a VM role.Read Windows Azure Diagnostics: Initializing the Configuration and Using a Configuration File in full
MDX is a powerful, yet complex language. Many terms and concepts need to be understood well enough if you want to master it. In order to help you in that mission, this article will provide with a short explanation of all important terms related to MDX.
In this article by Tomislav Piasevoli, author of MDX with Microsoft SQL Server 2008 R2 Analysis Services Cookbook, we start by explaining what MDX queries are made of, followed by the terms and concepts specific to the execution of MDX queries. The middle part of the article covers the most important things related to dimension design, cube design, and MDX script. Next, we explain terms related to query optimization and finally finish the article with types of queries that can be used with SQL Server Analysis Services.Read Terms and Concepts Related to MDX in full
In early 2010, when you went to the Oracle Technology Network (OTN) website, it had just one link called Information Integration. This link led you to a simple web page that had information on Oracle-to-Oracle database-centric migration and integration tools such as SQL Loader, Data Pump, Oracle Streams, and Oracle Data Guard. The OTN website has been updated, but still lacks comprehensive coverage of the Oracle Information Integration stack.
In the previous article by Tom Laszewski, co-author of Oracle Information Integration, Migration, and Consolidation, we took a look at some oracle tools and products. In this article we will take a look at data services, data consolidation, data grid, information lifecycle management, oracle-to-oracle data integration, and application integration.Read Oracle Integration and Consolidation Products in full