Friday, April 6, 2007

How to Access Sql Server 2005 Remotely

If enabled, the default instance of the Microsoft SQL Server Database Engine

listens on TCP port 1433. Named instances of the SQL Server Database Engine and

SQL Server Mobile are configured for dynamic ports, which means they select an

available port when the SQL Server service is started. When connecting to a

named instance through a firewall, configure the Database Engine to listen on a

specific port, so that the appropriate port can be opened in the firewall.

To

assign a TCP/IP port number to the SQL Server Database Engine

  1. In SQL Server Configuration Manager, in the console pane, expand

    SQL Server 2005 Network Configuration, expand Protocols for

    , and then double-click TCP/IP.





  2. In the TCP/IP Properties dialog box, on the IP Addresses tab,

    several IP addresses appear, in the format IP1, IP2, up to

    IPAll. One of these are for the IP address of the loopback adapter,

    127.0.0.1. Additional IP addresses appear for each IP Address on the computer.

    Right-click each address, and then click Properties to identify the IP

    address that you wish to configure.





  3. If the TCP Dynamic Ports dialog box contains 0,

    indicating the Database Engine is listening on dynamic ports, delete the

    0.





  4. In the IPn Properties area box, in the TCP

    Port
    box, type the port number you wish this IP address to listen on, and

    then click OK.





  5. In the console pane, click SQL Server 2005

    Services
    .





  6. In the details pane, right-click SQL Server (

    name>) and then click restart, to stop and restart SQL

    Server.



After you have configured SQL Server to listen on a specific port

there are three ways to connect to a specific port with a client

application:



  • Run the SQL Server Browser service on the server to connect to the Database

    Engine instance by name.





  • Create an alias on the client, specifying the port number.





  • Program the client to connect using a custom connection string.



Powered by ScribeFire.

No comments: