Question regarding Instance

If I do a default SQL Server installation, and then find that I'd like to
have several instances installed after all, will I be stuck?
Thanks,
- Joe Geretz -
Hi,
When ever you do a new SQL server Installation after a default installation,
The Installation program will identify the old instance
and will create a NEW NAMED INSTANCE automatically.
All the subsequent installation after the default installation the server
name will be "MACHINENAME\<NAME YOU GIVE>"
So no worry, you will never get struck.
Thanks
Hari
MCDBA
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:#lMllL4FEHA.1396@.TK2MSFTNGP11.phx.gbl...
> If I do a default SQL Server installation, and then find that I'd like to
> have several instances installed after all, will I be stuck?
> Thanks,
> - Joe Geretz -
>

Question regarding Instance

If I do a default SQL Server installation, and then find that I'd like to
have several instances installed after all, will I be stuck?
Thanks,
- Joe Geretz -Hi,
When ever you do a new SQL server Installation after a default installation,
The Installation program will identify the old instance
and will create a NEW NAMED INSTANCE automatically.
All the subsequent installation after the default installation the server
name will be "MACHINENAME\<NAME YOU GIVE>"
So no worry, you will never get struck.
Thanks
Hari
MCDBA
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:#lMllL4FEHA.1396@.TK2MSFTNGP11.phx.gbl...
> If I do a default SQL Server installation, and then find that I'd like to
> have several instances installed after all, will I be stuck?
> Thanks,
> - Joe Geretz -
>

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.
>

question on memory

Win2K Advanced Server
SQL2K Enterprise
I need to set up 1 big fat Disaster Recovery box for my 6 production boxes.
I will do this by putting 6 instances of SQL on the DR box. I know that
there is an 8 gig max (using AWE) limit. But what I don't know is can each
instance have its own 8 gigs, or do all 6 instances need to share the same 8
gigs? Also, would switching to Win2K3 help me to be able to use more RAM?
Basically, I dont want to tell anyone to order 48 gigs or RAM (6 instances
with 8 gigs each) when Im only going to be able to use 8.
TIA, ChrisR
Chris,
Each instance can use it's own block of memory but I don't think Win2K Adv
server can use more than 8GB. I believe you need Data Center for more than
8GB. Certainly for 48GB. Do you need 8GB for each instance? Do each of
the 6 Prod boxes have 8GB now? Does your DR plan say you need to run all 6
instances on the one box at the same time? Seems kind of silly to have 6
individual boxes in prod and expect to run all 6 instances at once on one
box. In any case Win2K3 will not allow you to use any more ram but it does
have certain performance enhancements over 2K that you should take advantage
of.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
> Win2K Advanced Server
> SQL2K Enterprise
> I need to set up 1 big fat Disaster Recovery box for my 6 production
> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
> that there is an 8 gig max (using AWE) limit. But what I don't know is can
> each instance have its own 8 gigs, or do all 6 instances need to share the
> same 8 gigs? Also, would switching to Win2K3 help me to be able to use
> more RAM? Basically, I dont want to tell anyone to order 48 gigs or RAM (6
> instances with 8 gigs each) when Im only going to be able to use 8.
>
> TIA, ChrisR
>
|||I typed out a reply yesterday but I guess I forgot to hit the reply button.
No I don't need 8 gigs per instance, but 6 boxes sharing 8 gigs wont do
either. Yes, all of them may need to be on at once.
Thanks Andrew.
CR
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23MHGH$jYFHA.1152@.tk2msftngp13.phx.gbl...
> Chris,
> Each instance can use it's own block of memory but I don't think Win2K Adv
> server can use more than 8GB. I believe you need Data Center for more
> than 8GB. Certainly for 48GB. Do you need 8GB for each instance? Do
> each of the 6 Prod boxes have 8GB now? Does your DR plan say you need to
> run all 6 instances on the one box at the same time? Seems kind of silly
> to have 6 individual boxes in prod and expect to run all 6 instances at
> once on one box. In any case Win2K3 will not allow you to use any more
> ram but it does have certain performance enhancements over 2K that you
> should take advantage of.
> --
> Andrew J. Kelly SQL MVP
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
>

question on memory

Win2K Advanced Server
SQL2K Enterprise
I need to set up 1 big fat Disaster Recovery box for my 6 production boxes.
I will do this by putting 6 instances of SQL on the DR box. I know that
there is an 8 gig max (using AWE) limit. But what I don't know is can each
instance have its own 8 gigs, or do all 6 instances need to share the same 8
gigs? Also, would switching to Win2K3 help me to be able to use more RAM?
Basically, I dont want to tell anyone to order 48 gigs or RAM (6 instances
with 8 gigs each) when Im only going to be able to use 8.
TIA, ChrisRChris,
Each instance can use it's own block of memory but I don't think Win2K Adv
server can use more than 8GB. I believe you need Data Center for more than
8GB. Certainly for 48GB. Do you need 8GB for each instance? Do each of
the 6 Prod boxes have 8GB now? Does your DR plan say you need to run all 6
instances on the one box at the same time? Seems kind of silly to have 6
individual boxes in prod and expect to run all 6 instances at once on one
box. In any case Win2K3 will not allow you to use any more ram but it does
have certain performance enhancements over 2K that you should take advantage
of.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
> Win2K Advanced Server
> SQL2K Enterprise
> I need to set up 1 big fat Disaster Recovery box for my 6 production
> boxes. I will do this by putting 6 instances of SQL on the DR box. I know
> that there is an 8 gig max (using AWE) limit. But what I don't know is can
> each instance have its own 8 gigs, or do all 6 instances need to share the
> same 8 gigs? Also, would switching to Win2K3 help me to be able to use
> more RAM? Basically, I dont want to tell anyone to order 48 gigs or RAM (6
> instances with 8 gigs each) when Im only going to be able to use 8.
>
> TIA, ChrisR
>|||I typed out a reply yesterday but I guess I forgot to hit the reply button.
No I don't need 8 gigs per instance, but 6 boxes sharing 8 gigs wont do
either. Yes, all of them may need to be on at once.
Thanks Andrew.
CR
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23MHGH$jYFHA.1152@.tk2msftngp13.phx.gbl...
> Chris,
> Each instance can use it's own block of memory but I don't think Win2K Adv
> server can use more than 8GB. I believe you need Data Center for more
> than 8GB. Certainly for 48GB. Do you need 8GB for each instance? Do
> each of the 6 Prod boxes have 8GB now? Does your DR plan say you need to
> run all 6 instances on the one box at the same time? Seems kind of silly
> to have 6 individual boxes in prod and expect to run all 6 instances at
> once on one box. In any case Win2K3 will not allow you to use any more
> ram but it does have certain performance enhancements over 2K that you
> should take advantage of.
> --
> Andrew J. Kelly SQL MVP
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:euDyuWiYFHA.2380@.tk2msftngp13.phx.gbl...
>