ArcSDE DBMS Configuration Alternatives
ESRI recommends use of the Direct Connect as the preferred deployment architecture. Software improvements introduced with the 2004 ArcGIS 9.0 release removed user performance as a potential concern in selecting your ArcSDE configuration. This section provides an overview of why ESRI recommends ArcSDE direct connect as the preferred geodatabase architecture.
Contents
ArcSDE Configuration Options
Figure 7a-1 shows the three configuration options for connecting ArcGIS applications to an ArcSDE Geodatabase.
ArcSDE Client Performance Comparison
Figure 7a-2 shows a performance comparison between the ArcSDE Application Server Connect (ASC) and ArcSDE Direct Connect (DC) configuration options. User performance is roughly the same when comparing Unversioned and Versioned database configurations between the two configuration options (versioned geodatabase can perform slower than unversioned). The three tier (remote ArcSDE server) configuration may be slightly slower due to the additional platform communication interface.
Database Server Processing Load Comparison
A closer look at the database server processing load will highlight the real advantages of the direct connect architecture. When using an ArcSDE Direct Connection to the DBMS, the ArcSDE processing load is supported by the client application and not on the DBMS server. The ArcSDE processing load can be as heavy as the DBMS load, so removing ArcSDE processing from the DBMS server doubles the performance capacity of the data server platform. Figure 7a-3 takes a closer look at comparing the data server loads for the ASC and DC configurations. The Direct Connect options reduce the data server processing load by roughly 50 percent.
Database Server Capacity Comparison
There are several potential advantages for having a lighter DBMS server load. Peak capacity processing loads can be supported on a DBMS server with half the number of core (reduce DBMS licensing by up to 50 percent). Larger capacity Enterprise GIS systems can be supported by lower cost server platform technology.
ESRI changed how we license ArcSDE with the ArcGIS 9.2 release - we no longer count the DBMS server core when using an ArcSDE Direct Connect architecture (ArcSDE GSRVR executables not installed on the DBMS server).
There were some limitations with the earlier ArcGIS 9 release that led many users to continue supporting ArcSDE executables on the DBMS server. One limitation restricted client applications from connecting to an earlier release geodatabase (ArcSDE executable will connect only to the same version geodatabase configuration). The ArcGIS 9.3 release includes drivers for connecting direct connect clients to previous version geodatabase schema.
Figure 7a-4 shows the capacity change when using a direct connect architecture. The ArcSDE Direct Connect architecture can increase DBMS server capacity by more than 50 percent.
CPT Calculator ArcSDE Architecture Performance Comparison
Figure 7a-5 shows how the ArcSDE Architecture connections are made in the CPT Calculator (DC-Direct Connect or ASC-Application Server Connect) using the platform architecture selection in cell A11. The top left result shows an ArcGIS Server 9.3.1 REST Web mapping workflow in a two tier server configuration with ArcSDE GSRVR installed on the DBMS platform (ASC connect). The bottom right result shows the same Web mapping workflow with an ArcSDE Direct Connect configuration.
User performance is roughly the same for both configuration options (0.5 seconds for local users) and remote user traffic is the same. Web server load increases from 43 to 51 percent, and the DBMS server load decreases from 15 to 7.5 percent. The DBMS server peak capacity increases from 442 to 884 users.
Many ESRI customers continue to configure ArcSDE on the DBMS server. Most customers are moving to a direct connect architecture to simplify administration and reduce licensing costs. ESRI continues to fully support both ArcSDE geodatabase configuration strategies.
[Return to ArcSDE DBMS Configure Alternative 27th Edition]
