February 23, 2010 at 4:04 am
Change in the port number for sql server
I need to change my sql server port number from 1433 to something unknown. As per the new security policy released in our project. I am lead here and what the best I could find on net is following link:
http://www.lockergnome.com/sqlsquirrel/2008/01/16/locating-server-port-in-sql-server-2005/
Are there any special considerations while changing the port number.
-Lk
February 23, 2010 at 5:14 am
I have to admit that it is a long time since I’ve changed the default port, bus as far as I remember, you’ll have to select a fixed port number, so you’ll be able to configure the firewall only once and not each time that the service is rebooted. You’ll also have to modify the connection strings that work with the server so they’ll specify the new port. An alternative is to work with the client configuration utility and create an alias that includes the new port number.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 23, 2010 at 10:25 pm
I'm assuming by unknown you mean non-default?
You can use a dynamically-assigned (at startup) port but as Adi said, you might run into firewall issues depending on your setup. If you just want to use something different to 1433 then you can statically assign a port, and if you turn on the SQL Browser service then apps should be able to connect without specifying the port.
If you use Kerberos you may need to assign the SPN unless the service account has permissions to do that itself.
February 23, 2010 at 10:52 pm
I researched this issue a few days ago.
I would change the IP Address of the Default instance from 1433 to an available port.
I would turn of the Browser Service for it is a security risk.
You will need to assign Static IP's to named instances
You should use Alias as well.
Another consideration is what protocol to use.
I welcome a constructive diagloge on this issue.
I appreciate any thoughts with respect to best practices with respect to security, performance, etc.
Please refer to the following links:
Using Non-Standard Port for SQL Server
How to configure an instance of SQL Server to listen on a specific TCP port or dynamic port
http://support.microsoft.com/kb/823938
Configuring the Windows Firewall to Allow SQL Server Access
http://msdn.microsoft.com/en-us/library/cc646023.aspx
Choosing a Network Protocol
http://msdn.microsoft.com/en-us/library/ms187892.aspx
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply