Post reply

How to redirect a port in sql server

  • June 15, 2009 at 10:39 pm

    #1010018

    I'm not sure you have your arms around how SQL server uses ports.

    SQL server cannot listen to multiple ports. one port per instance default is 1433, as you know, and you can change it... but you can only change it from one port to another, not use multiple ports.

    it is not like a web server, where you can have lots of virtual instances/pages answering different ports.

    forget about trying to play with ports.

    remember you could connect to a SQL server via named pipes, and never use TCP/IP and ports.

    you can even set up some other protocols as well, but I've never bothered. the whole purpose is to allow users to connect to a server, use security to login, and pass queries to the server.

    only if your customers are outside of your network would you consider poking a hole in the firewall, opening up an odd port number, and using port forwarding to get them to connect to your server.

    you should use SQL Security to determine what your customers can or cannot do. ports are for the network guy, not the DBA to fiddle with.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • June 18, 2009 at 2:05 am

    #1011506

    Hi, in a business environment you could have two servers. One SQL server for development (with 1436) and the other SQL server intance for production (with 1433).

    If your operative system is server, also you have port redirection/fordwarding service.

    In SQL 2005/2008 the port assigment is dyamic. This is more secure from injections and attacks to your database. But you can put it fixed (not recomended). Also you could activate pipe connections and tcp connections. But in this case is recomended that you have a firewall device inside your organization.

    SQL server is a database server not is a firewall server like ISA server. Then you can manage data but can't do it with system communications.

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply