Showing posts with label tcp. Show all posts
Showing posts with label tcp. Show all posts

Monday, March 12, 2012

Question on named instance

Hi,
I have sql2000 and 2 instances running, none have the default port. From the
BOL:
"A TCP port is chosen dynamically the first time the MSSQL$instancename
service is started."
"SQL Server 2000 clients do not have to be configured to connect to an
instance of SQL Server 2000. The SQL Server 2000 client components query a
computer running instances of SQL Server 2000 to determine the Net-Libraries
and network addresses for each instance. The client components then
transparently choose a supported Net-Library and address for the connection
without having to be configured on the client. The only information the
application must supply is the computer name and instance name."
Questions:
1, If I restart the MSSQL$instancename service the port is going to change
or fixed there?
2, what is "client components" refers to?
2, I need to connect to these instances from jdbc which only needs server
name and port number which is different from the above statement, how can I
connect?
Thanks
> 1, If I restart the MSSQL$instancename service the port is going to
change
> or fixed there?
I have no idea about this. If I had to guess, I would say that it
doesn't change. Suppose that a client obtains the port number for an
instance, then the instance gets restarted; now the client has an
incorrect port number (if the port has changed) and it has to get all
that information again. But this is just a guess.

> 2, what is "client components" refers to?
MDAC, JDBC drivers, any client libraries.

> 2, I need to connect to these instances from jdbc which only needs
server
> name and port number which is different from the above statement, how
can I
> connect?
You can look into the registry and obtain the port number from there
(not sure exactly where, but you could google for it) or you could use
a JDBC driver that "knows" how to determine ports for named instances,
such as the open source jTDS or the commercial drivers.
Alin.
Disclaimer: I am a jTDS developer.
|||Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:

> change
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
>
> MDAC, JDBC drivers, any client libraries.
> server
> can I
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the open source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>
|||The automatic assignment of ports on named instances that WERE NOT
configured manually do not change. However, upon startup, the first time,
one is acquired and cached. Upon secondary startups, if that same port is
in use by another process, then SQL Server will attempt binding to a new
port number.
What is meant by port assignment on the client end is that SQL Server
exposes UDP 1434, called Dynamic Discovery. Anyone who queries this will
receive a list of instances and port assignments which will automatically
configure clients to connect to those ports.
Sincerely,
Anthony Thomas

"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:932AC1DF-7195-416B-8DD6-6110BFEB4086@.microsoft.com...
Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:

> change
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
>
> MDAC, JDBC drivers, any client libraries.
> server
> can I
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the open source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>

Question on named instance

Hi,
I have sql2000 and 2 instances running, none have the default port. From the
BOL:
"A TCP port is chosen dynamically the first time the MSSQL$instancename
service is started."
"SQL Server 2000 clients do not have to be configured to connect to an
instance of SQL Server 2000. The SQL Server 2000 client components query a
computer running instances of SQL Server 2000 to determine the Net-Libraries
and network addresses for each instance. The client components then
transparently choose a supported Net-Library and address for the connection
without having to be configured on the client. The only information the
application must supply is the computer name and instance name."
Questions:
1, If I restart the MSSQL$instancename service the port is going to change
or fixed there?
2, what is "client components" refers to?
2, I need to connect to these instances from jdbc which only needs server
name and port number which is different from the above statement, how can I
connect?
Thanks> 1, If I restart the MSSQL$instancename service the port is going to
change
> or fixed there?
I have no idea about this. If I had to guess, I would say that it
doesn't change. Suppose that a client obtains the port number for an
instance, then the instance gets restarted; now the client has an
incorrect port number (if the port has changed) and it has to get all
that information again. But this is just a guess.

> 2, what is "client components" refers to?
MDAC, JDBC drivers, any client libraries.

> 2, I need to connect to these instances from jdbc which only needs
server
> name and port number which is different from the above statement, how
can I
> connect?
You can look into the registry and obtain the port number from there
(not sure exactly where, but you could google for it) or you could use
a JDBC driver that "knows" how to determine ports for named instances,
such as the Open Source jTDS or the commercial drivers.
Alin.
Disclaimer: I am a jTDS developer.|||Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:

> change
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
>
> MDAC, JDBC drivers, any client libraries.
>
> server
> can I
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the Open Source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>|||The automatic assignment of ports on named instances that WERE NOT
configured manually do not change. However, upon startup, the first time,
one is acquired and cached. Upon secondary startups, if that same port is
in use by another process, then SQL Server will attempt binding to a new
port number.
What is meant by port assignment on the client end is that SQL Server
exposes UDP 1434, called Dynamic Discovery. Anyone who queries this will
receive a list of instances and port assignments which will automatically
configure clients to connect to those ports.
Sincerely,
Anthony Thomas
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:932AC1DF-7195-416B-8DD6-6110BFEB4086@.microsoft.com...
Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:

> change
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
>
> MDAC, JDBC drivers, any client libraries.
>
> server
> can I
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the Open Source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>

Question on named instance

Hi,
I have sql2000 and 2 instances running, none have the default port. From the
BOL:
"A TCP port is chosen dynamically the first time the MSSQL$instancename
service is started."
"SQL Server 2000 clients do not have to be configured to connect to an
instance of SQL Server 2000. The SQL Server 2000 client components query a
computer running instances of SQL Server 2000 to determine the Net-Libraries
and network addresses for each instance. The client components then
transparently choose a supported Net-Library and address for the connection
without having to be configured on the client. The only information the
application must supply is the computer name and instance name."
Questions:
1, If I restart the MSSQL$instancename service the port is going to change
or fixed there?
2, what is "client components" refers to?
2, I need to connect to these instances from jdbc which only needs server
name and port number which is different from the above statement, how can I
connect?
Thanks> 1, If I restart the MSSQL$instancename service the port is going to
change
> or fixed there?
I have no idea about this. If I had to guess, I would say that it
doesn't change. Suppose that a client obtains the port number for an
instance, then the instance gets restarted; now the client has an
incorrect port number (if the port has changed) and it has to get all
that information again. But this is just a guess.
> 2, what is "client components" refers to?
MDAC, JDBC drivers, any client libraries.
> 2, I need to connect to these instances from jdbc which only needs
server
> name and port number which is different from the above statement, how
can I
> connect?
You can look into the registry and obtain the port number from there
(not sure exactly where, but you could google for it) or you could use
a JDBC driver that "knows" how to determine ports for named instances,
such as the open source jTDS or the commercial drivers.
Alin.
Disclaimer: I am a jTDS developer.|||Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:
> > 1, If I restart the MSSQL$instancename service the port is going to
> change
> > or fixed there?
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
> > 2, what is "client components" refers to?
> MDAC, JDBC drivers, any client libraries.
> > 2, I need to connect to these instances from jdbc which only needs
> server
> > name and port number which is different from the above statement, how
> can I
> > connect?
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the open source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>|||The automatic assignment of ports on named instances that WERE NOT
configured manually do not change. However, upon startup, the first time,
one is acquired and cached. Upon secondary startups, if that same port is
in use by another process, then SQL Server will attempt binding to a new
port number.
What is meant by port assignment on the client end is that SQL Server
exposes UDP 1434, called Dynamic Discovery. Anyone who queries this will
receive a list of instances and port assignments which will automatically
configure clients to connect to those ports.
Sincerely,
Anthony Thomas
"John Bandettini" <JohnBandettini@.discussions.microsoft.com> wrote in
message news:932AC1DF-7195-416B-8DD6-6110BFEB4086@.microsoft.com...
Jen
The port the instance uses is fixed. You should find the default instance
will be running on port 1433. The named instance will be assigned by SQL
Server when you created the instance. If you want to see what ports you are
using, from the SQL Server programs group choose Server Network Utility (You
need to do this on the server running SQL Server). On there click on TCP/IP
and then properties, this will show you the port the instance is using.
Regards
John
"Alin Sinpalean" wrote:
> > 1, If I restart the MSSQL$instancename service the port is going to
> change
> > or fixed there?
> I have no idea about this. If I had to guess, I would say that it
> doesn't change. Suppose that a client obtains the port number for an
> instance, then the instance gets restarted; now the client has an
> incorrect port number (if the port has changed) and it has to get all
> that information again. But this is just a guess.
> > 2, what is "client components" refers to?
> MDAC, JDBC drivers, any client libraries.
> > 2, I need to connect to these instances from jdbc which only needs
> server
> > name and port number which is different from the above statement, how
> can I
> > connect?
> You can look into the registry and obtain the port number from there
> (not sure exactly where, but you could google for it) or you could use
> a JDBC driver that "knows" how to determine ports for named instances,
> such as the open source jTDS or the commercial drivers.
> Alin.
> Disclaimer: I am a jTDS developer.
>