基于web的社区阅览室信息系统开题报告(编辑修改稿)

基于web的社区阅览室信息系统开题报告(编辑修改稿)内容摘要：

Analysis Services Summary: Learn how to use the connection pooling objects included with the Microsoft XML for Analysis Provider to develop scalable client and Web applications for Microsoft SQL Server 20xx Analysis Services. Connection Pooling Objects Two objects, ADOConPool and OLEDBConPool, are available through the XML for Analysis Provider. The ADOConPool object manages ADO connection objects. The OLEDBConPool object manages OLE DB session objects. Although each object supplies a different type of connection pool, they both use the same underlying mechanisms to manage the connection pool. For the purposes of this white paper, the term connection is used to describe both ADO connection objects and OLE DB session objects when discussing such shared mechanisms. The connection pooling mechanism is intended for use only with the updated Microsoft OLE DB Provider for OLAP Services () OLE DB provider included with the Microsoft SQL Server 20xx Service Pack 1 (SP1). Using the Connection Pooling Objects You can use the ADOConPool and OLEDBConPool objects with any programming language that supports ADO or OLE DB data access technologies. However, to use these objects in a Visual C++ program, you must add the following piler directives to your program to include the correct headers and attributes: include include import filepath\\ rename(tag_inner_PROPVARIANT, tagPROPVARIANT) rename(_LARGE_INTEGER,) rename(_ULARGE_INTEGER,) using namespace MSXmlAnalysisSCLib。 Requesting and Returning Connections The mechanism used to request connections from the connection pool is different from the mechanism typically employed by OLE DB resource pooling to facilitate fast access for Webbased applications. The connection pool object breaks the pool of active connections into two groups: free connections and used connections. Free connections consist of connections that are not currently allocated to a client application. Used connections are currently allocated to and in use by client applications. A special authentication and impersonation mechanism is employed for connection requests. When a connection is requested by an application (using either the GetConnection method for the ADOConPool object or the GetSession method for the OLEDBConPool object), the connection pool attempts to retrieve a free connection that uses the same domain and user name as the security identifier (SID) used by the client application. If a match is found, the free connection is returned to the client application. If a match based on the client SID information is not found, the connection pool object parses the connection information that was passed in the client request to determine whether a free connection for the same requested database already exists in the connection pool. If a database match is found, the connection pool object attempts to match the role security of the client request to the role security of the existing free connection. If a role security match is found, the connection pool object pares the user nam。