Client/Server Architecture and Data Access - Microsoft SQL Server 2008 Analysis Services - page 565

CHAPTER 31

IN THIS CHAPTER

. Using TCP/IP for Data Access

Client/Server
Architecture and Data
Access

. Using HTTP for Data Access

. Offline Access to Data

. Client Components Shipped

with Analysis Services

A nalysis Services supports several types of data access
architectures. The most straightforward architecture is made
up of a client and a server, generally located on distinct
computers, communicating directly with each other. If you
want to communicate via the Internet, we need to intro-
duce a middleware component, Internet Information
Services (IIS), which serves as a bridge between the client
and the server. Analysis Services also supports an offline
scenario, in which you browse your data within a local cube ;
this architecture combines the client and server on the
same computer and inside the same process.

Using TCP/IP for Data Access

When both the client and the server are located within the
same domain, connections to Analysis Services are usually
made through TCP/IP. In this case, messages traverse a four-
layer protocol stack (see Figure 31.1):

. Internet Protocol (IP) is responsible for addressing and

defining the route from one computer to another.

. Transmission Control Protocol (TCP) is used for trans-

ferring blocks of data that don't bear semantic
loading.

. Simple Object Access Protocol (SOAP) is a lightweight

protocol that uses an Extensible Markup Language
(XML) messaging framework to transfer information
between applications.