blog.Toby

            BlogJava :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理 ::
            130 隨筆 :: 2 文章 :: 150 評論 :: 0 Trackbacks
          Clients (Analysis Services - Multidimensional Data)
          [This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

          Microsoft SQL Server Analysis Services supports a thin client architecture. The Analysis Services calculation engine is entirely server-based, so all queries are resolved on the server. As a result, only a single round trip between the client and the server is required for each query, resulting in scalable performance as queries increase in complexity.

          The native protocol for Analysis Services is XML for Analysis (XML/A). Analysis Services provides several data access interfaces for client applications, but all of these components communicate with an instance of Analysis Services using XML for Analysis.

          Several different providers are provided with Analysis Services to support different programming languages. A provider communicates with an Analysis Services server by sending and receiving XML for Analysis in SOAP packets over TCP/IP or over HTTP through Internet Information Services (IIS). An HTTP connection uses a COM object instantiated by IIS, called a data pump, which acts as a conduit for Analysis Services data. The data pump does not examine the underlying data contained in the HTTP stream in any way, nor are any of the underlying data structures available to any of the code in the data library itself.

          Logical client architecture for Analysis Services

          Win32 client applications can connect to an Analysis Services server using OLE DB for OLAP interfaces or the Microsoft® ActiveX® Data Objects (ADO) object model for Component Object Model (COM) automation languages, such as Microsoft Visual Basic®. Applications coded with .NET languages can connect to an Analysis Services server using ADO MD.NET.

          Existing applications can communicate with Analysis Services without modification simply by using one of the Analysis Services providers.

          Programming Language Data Access Interface

          C++

          OLE DB for OLAP

          Visual Basic 6

          ADO MD

          .NET languages

          ADO MD.Net

          Any language that supports SOAP

          XML for Analysis

          Analysis Services has a Web architecture with a fully scalable middle tier for deployment by both small and large organizations. Analysis Services provides broad middle tier support for Web services. ASP applications are supported by OLE DB for OLAP and ADO MD, ASP.NET applications are supported by ADOMD.NET. The middle tier, illustrated in the following figure, is scalable to many concurrent users.

          Logical diagram for middle-tier architecture

          Both client and middle tier applications can communicate directly with Analysis Services without using a provider. Client and middle tier applications may send XML for Analysis in SOAP packets over TCP/IP, HTTP, or HTTPS. The client may be coded using any language that supports SOAP. Communication in this case is most easily managed by Internet Information Services (IIS) using HTTP, although a direct connection to the server using TCP/IP may also be coded. This is the thinnest possible client solution for Analysis Services.

          posted on 2008-08-15 10:00 渠上月 閱讀(181) 評論(0)  編輯  收藏 所屬分類: OLAP
          主站蜘蛛池模板: 石楼县| 邻水| 石林| 自治县| 霸州市| 临颍县| 余姚市| 桐柏县| 吉木乃县| 汨罗市| 富源县| 交口县| 阳东县| 永城市| 茌平县| 自治县| 岳阳市| 额济纳旗| 青海省| 青神县| 武宁县| 藁城市| 南雄市| 阿城市| 韩城市| 舒城县| 黎平县| 六安市| 巫溪县| 花莲县| 濮阳市| 防城港市| 沭阳县| 五华县| 吴堡县| 库伦旗| 滦南县| 宜兰县| 舒城县| 增城市| 焦作市|