klwn
asked on
MS SQL Server 2008 listening on additional port
Dear Experts Exchange,
We have a SQL Server 2008 server (standard edition) which hosts a number of live databases on one instance. We need to setup a new database on this sql instance which has connectivity to a website. This website needs to connect over a different port (as opposed to using the default 1433) to the new database.
We are proposing to add the new port in the 'SQL Server Configuration Manager' under the 'Sql Server Network Configuration' > 'Protocols for Mssqlserver > 'TCP/IP' properties and specifying it in the 'Ip Adresses' tab by putting a comma next to the default port 1433 and adding the new port there (this is in the 'TCP Port' box which is under the headings IP1, IP2, IP3 and IPAll).
Once the above changes have been made we are proposing to restart the MSSQLSERVER service through the Configuration Manager in order for the changes to take effect.
Are there any considerations that we need to make for this change as we don't want to affect the current live databases on this instance which we are assuming are only listening on port 1433 currently as this is the only one specified in the configuration described above?
Your advice on the above would be greatly appreciated.
Kind regards,
Amy
We have a SQL Server 2008 server (standard edition) which hosts a number of live databases on one instance. We need to setup a new database on this sql instance which has connectivity to a website. This website needs to connect over a different port (as opposed to using the default 1433) to the new database.
We are proposing to add the new port in the 'SQL Server Configuration Manager' under the 'Sql Server Network Configuration' > 'Protocols for Mssqlserver > 'TCP/IP' properties and specifying it in the 'Ip Adresses' tab by putting a comma next to the default port 1433 and adding the new port there (this is in the 'TCP Port' box which is under the headings IP1, IP2, IP3 and IPAll).
Once the above changes have been made we are proposing to restart the MSSQLSERVER service through the Configuration Manager in order for the changes to take effect.
Are there any considerations that we need to make for this change as we don't want to affect the current live databases on this instance which we are assuming are only listening on port 1433 currently as this is the only one specified in the configuration described above?
Your advice on the above would be greatly appreciated.
Kind regards,
Amy
ASKER
Hi Mohammed,
Our application vendor will be specifying within their website configuration which port should be used to access the database on the SQL Server 2008 instance (this will be the new port) and we will have a firewall rule in place to route the website traffic to the server using the new port.
Therefore if we went with our original plan in my question, can you see this being an issue? Our main concern is that we don't want to affect the current live databases already on this instance, which could already be listening on the default port?
Our application vendor will be specifying within their website configuration which port should be used to access the database on the SQL Server 2008 instance (this will be the new port) and we will have a firewall rule in place to route the website traffic to the server using the new port.
Therefore if we went with our original plan in my question, can you see this being an issue? Our main concern is that we don't want to affect the current live databases already on this instance, which could already be listening on the default port?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have used the additional IP method to a specific application where the vendor did not recommend adding two port to the listener.