ArcSDE direct connect

From Wiki.GIS.com

This article may need to have categories added to fit within wiki.gis.com's taxonomy. You can help. The discussion page may contain suggestions.

This article is missing citations or needs footnotes. Please help add inline citations to guard against copyright violations and factual inaccuracies.

This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed.

This article may need to be rewritten entirely to comply with wiki.gis.com's Terms of Use. You can help. The discussion page may contain suggestions.

ArcSDE Direct Connect, also called a two-tier connect is a method of connecting directly to a ArcSDE Geodatabase without using an ArcSDE application server. This only involves a two-tier configuration, in which the client application directly communicates with the database. ArcSDE License is required for a Direct Connect even though the Client is directly communicating with the Database.

• ArcSDE Direct Connects utilise the resources from the Client machine for processing and there by reduce load on the Server. In environments where Client machines have good resources and Servers are heavily accessed with Application Server Connections, Direct Connects become an obvious choice.

• Administering a Direct Connect is not so easy for an ArcSDE administrator. Since this type of Connection does not go through the ArcSDE Service, disconnecting it is a tedious process. It can be easily disconnected either at the Client machine or by restarting a Database service which is not often an option.

Contents 1 Setting up a Direct Connect 1.1 Oracle 1.2 SQL Server 2 Further Reading

[edit] Setting up a Direct Connect

Client machines need to be configured based on the Geodatabase being connected to. Steps to follow in setting up a Client machine to connect directly to an ArcSDE geodatabase on each supported database management system (DBMS) are:

[edit] Oracle

Configuring a Direct Connect for Oracle DBMS needs installation of Oracle Client and configuring a Netservice name locally on the Client machine, the tnsnames.ora file be altered on the client, and an ODBC connection created.

[edit] SQL Server

As long as the Client machine is up-to-date with the Microsoft Data Access Components (MDAC) components and the OLE DB Drivers for SQL Server no additional configuration is required. However, if the Client OS is not up-to-date installing the SQL Server Native Client installs the necessary components.

[edit] Further Reading

• Properties of a direct connection to an ArcSDE geodatabase ArcGIS 9.3 Desktop online help.Accessed 18 August 2010.