How To: Install ArcSDE 9.2/9.3 and Microsoft SQL Server 2005 on separate servers with a distributed install
Instructions provided describe how to install ArcSDE 9.2/9.3 and Microsoft SQL Server 2005 on separate servers with a distributed installation. This is not specifically recommended as the default installation type but is sometimes necessary that ArcSDE and SQL Server are distributed on two separate servers.
In most cases, ArcSDE can be installed against SQL Server on another remote server without additional setup steps because the SQL Server Agent service can be used to connect to an instance of SQL Server over named pipes by using dynamic server names.
If the default settings for network transport are changed, or a connection is made to an instance of SQL Server that listens on an alternate named pipe, additional steps are necessary for the client and server machines to communicate.
Otherwise, this installation requires no additional client configuration if everything from the initial installation of the database is kept as default.
For the installation procedures for ArcSDE, refer to the Installation Guide available on the DVD media for ArcSDE 9.2/9.3.
- Set up and configure a client alias on the ArcSDE machine if needed.
The use of a client alias is only necessary if the SQL Server instance name in the ArcSDE Post Installation Wizard cannot be used.
The following document gives directions on configuring a SQL Server alias on the ArcSDE client machine for SQL server 2005 in SQL Server Management Studio:
How to: Create a Server Alias for Use by a Client (SQL Server Configuration Manager)
- Run the ArcSDE Post Installation Wizard on the ArcSDE machine:
Use the alias name that was set up for the remote SQL Server instance in place of the SQL Server instance name in the according parameter fields throughout the Post Installation Wizard.