Microsoft Certification Examples, exercises, practises, tutorials, solutions about Database

Change page: < 1 2 3 4 5 6 7 8 9 10 11 > | Displaying page 7 of 11, items 181 to 210 of 326.

SQL Azure : Managing Your Azure Projects

Now you're getting to the meat of Azure. After reading all the information in the last two chapters, and working through setup and activation in this chapter, the time has come to start getting your hands dirty. From here on out, it's hands-on.

SQL Azure : Creating Your Azure Account

Creating an Azure account is simple, but it takes quite a few steps because of the amount of information required.

An OLAP Requirements Example: CompSales International (part 16) - Security and Roles

Security is straightforward in SSAS. For each database or cube, roles are identified with varying levels of granularity for users. Roles are used when accessing the data in cubes. The process works like this: a role is defined, and then an individual user or group who is a member of that role is assigned that role.

An OLAP Requirements Example: CompSales International (part 15) - SSIS

Data mining is the process of understanding potentially undiscovered characteristics or distributions of data. Data mining can be extremely useful for OLAP database design in that patterns or values might define different hierarchy levels or dimensions that were not previously known.

An OLAP Requirements Example: CompSales International (part 14) - Data Mining

An OLAP Requirements Example: CompSales International (part 13) - Cube Perspectives

A new feature in SSAS is cube perspectives. This is essentially a way to create working views of a complex cube that is focused on just what a particular user or group of users need.

An OLAP Requirements Example: CompSales International (part 12) - Generating a Relational Database

Designing dimensional databases is an art form and requires not only sound dimensional modeling knowledge, but also knowledge of the business processes with which you are dealing.

An OLAP Requirements Example: CompSales International (part 11)

Remember from the Comp Sales requirements that there was an additional user need to see the difference between sales units and sales returns (sales units minus sales returns) to yield net sales

An OLAP Requirements Example: CompSales International (part 10)

ADO MD is an easy-to-use access method for dimensional data via an OLE DB for OLAP provider. You can use ADO MD in Visual Basic, Visual C++, and Visual J++.

An OLAP Requirements Example: CompSales International (part 9) - Browsing Data in the Cube

Now you can process actual data into your cube from the data source view. To do so, you right-click the Comp Sales cube entry in the Solution Explorer and choose the Process item or choose the Process icon for the cube in the cube designer (second icon from the left in the cube designer).

An OLAP Requirements Example: CompSales International (part 8) - Aggregating Data Within the Cube

An OLAP Requirements Example: CompSales International (part 7) - Building and Deploying the Cube

You basically have a cube definition now, but it is just an empty shell. You need to process it and then deploy it so that it is instantiated and populated with data (via the data source view).

An OLAP Requirements Example: CompSales International (part 6) - Creating the Cube

Most of the hard work in the CompSales International example is done. All that is left to do now is to create a cube that is based on your fact tables in your data source, use the dimensions and hierarchies you just defined, and then process it (that is, populate the cube with data)

An OLAP Requirements Example: CompSales International (part 5) - Creating the Other Dimensions

Now you essentially need to go through the whole process of creating a dimension and a hierarchy for the other dimensions (Product and Geography).

An OLAP Requirements Example: CompSales International (part 4) - Defining Dimensions and Hierarchies

You are now ready to start defining dimensions and hierarchies to your database. Dimensions are the building blocks for cubes in SSAS. You start by right-clicking the Dimensiond object in the Solution Explorer (or choosing Project, New Dimension).

An OLAP Requirements Example: CompSales International (part 3) - Creating Data Source Views

Creating a data source view essentially allows you to look more deeply into the metadata of the data source and add additional relationships, create things like calculations, and set logical keys on the metadata of the data source.

An OLAP Requirements Example: CompSales International (part 2) - Adding a Data Source

To add data sources for a new database, you simply right-click the Data Sources object in the Solution Explorer or select Project, New Data Source in Visual Studio. The Data Source Wizard is then initiated

An OLAP Requirements Example: CompSales International (part 1)

Following is an abbreviated requirement that reflects an actual implementation that was done for a large Silicon Valley company. We follow the mini-methodology as closely as possible to implement this requirement in SSAS, pointing out which facilities of SSAS should be used for which purpose along the way.

SQL Server 2008 Analysis Services : An Analytics Design Methodology

A data warehouse can be built from the top down or from the bottom up. To build a top-down warehouse, you need to form a complete picture or logical data model for the entire organization (or all the subsystems within the scope of the project, such as all financial systems)

SQL Azure : Other Considerations

Blobs are files that can be stored in Windows Azure. What is interesting about blobs is that they can be easily accessed through REST, there is no limit to the number of blobs that can be created, and each blob can contain as much as 50GB of data.

SQL Azure : Sample Design - Application SLA Monitoring

To put a few of the patterns in perspective, let's create a formal design around a system that monitors application performance service-level agreements (SLAs). In this design, a company already has a monitoring product that can audit activity in existing SQL Server databases at customer sites

SQL Azure : Combining Patterns

The previous design patterns provide the necessary basis to build systems with SQL Azure. Some of these patterns can be used as is, but you're very likely to combine patterns to deliver improved solutions

SQL Server 2008 Analysis Services : Understanding the SSAS Environment Wizards (part 2)

One of the primary goals of OLAP is to increase data retrieval speed for business-related queries that are critical to decisions. Very often, there is a need to broaden the scope of a business query or to drill down into more granular details of the query

SQL Server 2008 Analysis Services : Understanding the SSAS Environment Wizards (part 1)

Welcome to the “land of wizards.” This implementation of SSAS, as with older versions of SSAS, is heavily wizard oriented. SSAS has a Cube Wizard, a Dimension Wizard, a Partition Wizard, a Storage Design Wizard, a Usage Analysis Wizard, a Usage-Based Optimization Wizard, an Aggregation Wizard, a Calculated Cells Wizard, a Mining Model Wizard, and a few other wizards.

SQL Server 2008 Analysis Services : Understanding SSAS and OLAP

Because OLAP is at the heart of SSAS, you need to understand what it is and how it solves the requirements of decision makers in a business. As you might already know, data warehousing requirements typically include all the capability needed to report on a business’s transactional history, such as sales history.

SQL Azure : Design Patterns (part 3)

In the offloading pattern, the primary consumer represents an existing onsite application with its own database; but a subset of its data (or the entire database) is replicated to a cloud database using SQL Data Sync (or another mechanism).

SQL Azure : Design Patterns (part 2) - Sharding

So far, you've seen patterns that implement a single connection at a time. In a shard, multiple databases can be accessed simultaneously in a read and/or write fashion and can be located in a mixed environment (local and cloud).

SQL Azure : Design Patterns (part 1)

Let's review the important design patterns that use SQL Azure. Before designing your first cloud application, you should read this section to become familiar with a few design options.

SQL Azure : Design Factors (part 2)

You may also consider developing Azure services to keep the database connection to a local network, and send the data back to the client using SOAP or REST messages

SQL Azure : Design Factors (part 1)

Storing data in SQL Azure is similar to storing data in SQL Server. All you need to do is issue T-SQL statements and review some of the limitations of the syntax specific to SQL Azure, and off you go!