Installations of SQL Server and ArcSDE on separate servers
When you install SQL Server and ArcSDE on separate servers, there are three things to keep in mind.
- If you install SQL Server on a different computer than ArcSDE, ArcSDE acts as a client to the database. To make direct connections to the database, you must have the SQL Server Native Client installed on the ArcSDE server. The SQL Server Native Client you install must be at least the same release as the SQL Server database to which you are connecting. For example, if you are connecting to a SQL Server 2005 database, install the SQL Server 2005 or 2008 Native Client. If you are connecting to SQL Server 2008, install the SQL Server 2008 Native Client. You can download the SQL Server Native Client from Microsoft's Web site.
- Be aware that if you are using Windows-Authenticated users (including the ArcSDE administrative user) to connect to the database using an ArcSDE service, you cannot install SQL Server and ArcSDE on separate servers. You have two options if you want to use Windows Authentication:
- Install SQL Server and ArcSDE on separate servers but only use direct connections to connect to the geodatabase.
- Install SQL Server and ArcSDE on the same server. If SQL Server and ArcSDE are on the same server, it does not matter which type of connection you make to the geodatabase.
- If you want to use the ST_Raster storage type, which can only be used in a single-spatial database model ArcSDE geodatabase for Microsoft SQL Server 2008, you must copy specific files from SDEHOME to the SQL Server computer before installing or upgrading the ST_Raster type. See Installing the ST_Raster type in a remote SQL Server database for instructions.
8/19/2013