How do you setup a listener within SQL2008?

Question

How do you setup a listener within SQL2008?

dax.latchford

SSCommitted

Points: 1969
More actions
October 22, 2015 at 6:17 am

#301670

Hi - One of my colleagues has been asked to setup a listener within SQL. I'm assuming a starting point would be the Configuration Manager. Can anyone offer any advice please?
Kind Regards
Dax

Viewing 5 posts - 1 through 4 (of 4 total)

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Could you get more details on what is actually required?

The only 'listener' I'm familiar with is the Availability Groups listener, which is part of the Availability Groups HA feature, introduced in SQL 2012.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

BLOB EATER SSChampion Points: 14609 More actions · Answer 2

Reminds me of Oracle terminology, do you mean a specific TCP port?

dax.latchford SSCommitted Points: 1969 More actions · Answer 3

Hi - Many thanks for coming back to me. I have now received some additional information:

What my colleague is actually looking to do is to asign a DB to use an additional port & not to use the default 1433. I'm assuming this would be Network Configuration/Protocols, add a comma next to the default 1433 to use this port & to then restart the Instance service through configuration manager?

We're looking to make the change on a Test Server initially. Are there any considerations for this change, as we don't want to cause issues as all DB's albeit one will be using port 1433?

Many thanks in advance.

Regards

Dax

Lowell SSC Guru Points: 323518 More actions · Answer 4

in that case, the assumptions really incorrect.

an entire SQL Service listens to a specific port; on a default instance, the default port is 1433, but, yes, it can be changed in the configuration.

you cannot make a single database listen to a port, that's not how SQL works

you can install multiple services, each of which listens to a different port.

so you could install another instance, with one user database(along with the standard four built in databases), and have that listen to a specific port.

it would compete for resources with any other SQL instances on the same machine.

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!