Max Num of Worker Threads and User Connections/Logins

Hi everyone,
I need to know what is the relationship between the "Maxium Number of Worker Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy databases. On average, we see about 264 total sessions on the box and we were wondering if the max worker threads number, bumping it up would fix the issue.
Can anyone offer any suggestions?
Thanks in advance,
Errol Neal
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal
|||Okay. I understand that. Thanks!
But why are we having random login failures? We are per-processor licensing so I am confused. Its not that the login is timing out. They are outright failing and I know because I am doing a SQL Server Trace and watching them as they fail.
-- Wayne Snyder wrote: --
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>
|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org

Max Num of Worker Threads and User Connections/Logins

Hi everyone,
I need to know what is the relationship between the "Maxium Number of Worker
Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy
databases. On average, we see about 264 total sessions on the box and we we
re wondering if the max worker threads number, bumping it up would fix the i
ssue.
Can anyone offer any suggestions?
Thanks in advance,
Errol NealAs long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal|||Okay. I understand that. Thanks!
But why are we having random login failures? We are per-processor licensing
so I am confused. Its not that the login is timing out. They are outright fa
iling and I know because I am doing a SQL Server Trace and watching them as
they fail.
-- Wayne Snyder wrote: --
As long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt
my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.orgsql

Max Num of Worker Threads and User Connections/Logins

Hi everyone
I need to know what is the relationship between the "Maxium Number of Worker Threads" setting (default = 255) and user connections/sessions/logins.
From time to time, we are experiencing random login failure for several busy databases. On average, we see about 264 total sessions on the box and we were wondering if the max worker threads number, bumping it up would fix the issue.
Can anyone offer any suggestions
Thanks in advance
Errol NealAs long as there are fewer than "Max worker threads" number of connections,
each connection gets its own individual thread... Once you go over that
number, several connections will share the same thread... You can increase
the number of worker threads, but that uses more memory ( even if there are
fewer connections.)
Thread sharing could result in front end timeouts ( especially if the other
connection you are sharing the thread with is a busy one.)
"Errol U. Neal" <eneal@.enhtech.com> wrote in message
news:09B0F39B-1468-4069-A8A1-BF2AF2E645C8@.microsoft.com...
> Hi everyone,
> I need to know what is the relationship between the "Maxium Number of
Worker Threads" setting (default = 255) and user
connections/sessions/logins.
> From time to time, we are experiencing random login failure for several
busy databases. On average, we see about 264 total sessions on the box and
we were wondering if the max worker threads number, bumping it up would fix
the issue.
> Can anyone offer any suggestions?
>
> Thanks in advance,
>
> Errol Neal|||Do you see any errors on the SQL error log e.g. "could not spawn process
login thread" or similar ? We have seen these under conditions of high
memory contention especially in the MemToLeave area where new threads cannot
allocate enough memory to start.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Errol Uriel Neal" <eneal@.enhtech.com> wrote in message
news:94D7AB61-A7F2-4FA1-B19C-D79B64B3B23D@.microsoft.com...
> Okay. I understand that. Thanks!
> But why are we having random login failures? We are per-processor
licensing so I am confused. Its not that the login is timing out. They are
outright failing and I know because I am doing a SQL Server Trace and
watching them as they fail.
>
> -- Wayne Snyder wrote: --
> As long as there are fewer than "Max worker threads" number of
connections,
> each connection gets its own individual thread... Once you go over
that
> number, several connections will share the same thread... You can
increase
> the number of worker threads, but that uses more memory ( even if
there are
> fewer connections.)
> Thread sharing could result in front end timeouts ( especially if the
other
> connection you are sharing the thread with is a busy one.)
>|||No. There is nothing like that or remotely similiar to that in the logs.
I've been having this issue now for over a month. I even completely rebuilt my SQL Server because
of it.
-- Jasper Smith wrote: --
Do you see any errors on the SQL error log e.g. "could not spawn proces
login thread" or similar ? We have seen these under conditions of hig
memory contention especially in the MemToLeave area where new threads canno
allocate enough memory to start
--
HT
Jasper Smith (SQL Server MVP
I support PASS - the definitive, globa
community for SQL Server professionals
http://www.sqlpass.or

max connections?

Ok, yeah, I'm being lazy...
Any comments?Geseundheit ?

-PatP|||Thank you...Thank you very much...

x002548 has left the building....|||Originally posted by Pat Phelan
Geseundheit ?

-PatP

We will be amused if you can explicate in english...:D in advance.|||Originally posted by Satya
We will be amused if you can explicate in english...:D in advance. There is an enormous amount of rather obscure humor in this thread.

Brett's original post made about as much sense to me as a sneeze. Max connections of what to what? Me to the red head at the bar, max connections equals zero.

I responded with a German word/phrase that is the courteous response to a sneeze. I hoped to provoke a bit more explanation of what Brett meant.

Brett apparently picked my response as a reference to an old Elvis Pressley movie scene. He then carried that reference further.

Like I said, the whole thread is rather obscure. I found it funny, YMMV.

-PatP|||Great... thanks for the meticulous explanation... a part of Friday funnies.:) :D :cool:|||ok...ok...

a server allows connections, yes?

We use connection pooling...you can set the min and max that it will manage...

Is there an upper limit of connections allowed by the server or before performance degrades?

Or am I phrasing this totally wrong?

Is it 5:00 yet?|||Well, its not 17:00 for you, but for me it is... so in jovial mood:p

Then coming to original point :
Max Pool Size keyword is to determine how many connections the pool will hold.

By default, the Data Provider permits 100 connections to accumulate in each pool. This doesn't mean that you start with 100 SqlConnection objects or 100 connections, only that you can't create more than 100 connections per pool.

If you try to exceed the maximum limit you've set, your application will wait until you pass the ConnectionTimeout limit or until a connection becomes available in the pool, then raise an exception. Max Pool Size doesn't limit the number of pools you can createthat limit is determined by the number of SQL Server connections that your sa setting or license makes available (about 32,768 per cluster).|||Originally posted by Brett Kaiser
a server allows connections, yes? If properly configured, yes.
Originally posted by Brett Kaiser
We use connection pooling...you can set the min and max that it will manage...

Is there an upper limit of connections allowed by the server or before performance degrades? Yes. The connection pooling is typically done on the "client" side of the connection, although it can be done on both sides.

In general, you want to have enough "idle" connections to service any resonable load of connection requests. This is usually between 2-5% (rounded up) of your pooled connections idle. This can vary considerably in "spikey" usage situations.

Connection pooling allows near instant initiation of new connections, but it can waste unnecessary resources if misused.
Originally posted by Brett Kaiser
Is it 5:00 yet? Somewhere! Probably about Munich by now.

-PatP

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian
"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/com...si1203.mspx#EB
AA
Regards
JTC ^..^
|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>
|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/co...isi1203.mspx#EB
AA
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/community/columns/insider/iisi1203.mspx#EB
AA
--
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>sql

max connections pool reached

Hi,
Can anyone tell me if he ever got this issue and how he get the solution. In my asp.net 2.0 application i close always ma connexions to sqlserver in the finally clause (the open is in the try); I open 1 ou 2 connecxions per aspx page, i close them always (in the finally clause or at the bottum of the form). Sometimes, the application is down with the message
Can not open a new connexion, max pool size is reached !!!!

I host my application on a remote server, i have no performance issues, only this great problem !!!
i cant view the status of connexion on the sqlserver, so what can i do, or how shoud i develop my connection.
thanks in advance to all of yuo who will help me.
Imed.

Please visithttp://www.15seconds.com/issue/040830.htm as it has some connection pool optimization tips.

Hope that helps.

Max connections in sql server 2000 MSDE

Hi !

What is the max number of connections in sql server 2000 MSDE ?

I have found three opinions on the web: 5,8 and unlimited(32,768...)

Which is true ?

/hakan

I don't think there is any limit to the number of connections. . .

there is a throttle on performance based on number of concurrent connections. the actual number that triggers the throttle i beleive depends on build/sp.

that being said. . . if you build your app correctly and design you database properly, you could probably service 100 to 200 concurrent users of your windows app without seeing a performance hit and thousands of concurrent users of a web app. thats just an opinion, don't ask me to prove it. but I will keep repeating that until someone from MS tells me differently.

but, build you app/db improperly and it doesnt matter which version of sql server you use. performance is going to suck any way.

Max connections for SQl 2000 on Win XP Pro

Hi,
I'm a teacher in VB and use SQL 2000 on a laptop with Windows XP Pro.
My class has 20 students, can they connect to the sql database on my laptop?
Thanks inadvanced.
Danny
Greetings from BelgiumYes they can. I guess the students will be running very
small test queries against the sql server on your laptop.
>--Original Message--
>Hi,
>I'm a teacher in VB and use SQL 2000 on a laptop with
Windows XP Pro.
>My class has 20 students, can they connect to the sql
database on my laptop?
>Thanks inadvanced.
>Danny
>Greetings from Belgium
>
>.
>|||Why Not?
Scenario 1: If students want to work on SQL Server .
You all must be within the same network/domain.
Install SQL Server client in their PC and then configure
the client if needed. Usually SQLServer Client identifies
the other Servers in the same domain automatically. If the
server is in different domain, then you have to configure
the client(Use Named Piped Protocol/TCPIP).
Scenario 2: Just if the students want to connect and query
the SQL Server database from VB applications, then use
ODBC connectivity in your application.
Hope this helps. If not, please reply with your questions
in detail.
-SQLVarad (MCDBA-1999, MCSE-1999)
Greetings from USA
>--Original Message--
>Hi,
>I'm a teacher in VB and use SQL 2000 on a laptop with
Windows XP Pro.
>My class has 20 students, can they connect to the sql
database on my laptop?
>Thanks inadvanced.
>Danny
>Greetings from Belgium
>
>.
>|||<anonymous@.discussions.microsoft.com> schreef in bericht
news:02f901c398c2$79845960$a101280a@.phx.gbl...
> Yes they can. I guess the students will be running very
> small test queries against the sql server on your laptop.
>
Thanks for the quick answer.
Yes, its for learning ADO
What are the max connection for SQL server on XP Pro or Win 2000 Pro?
Is there a difference must I install Windows 2000 or Windows 2003 server on
the laptop for te connections to te SQL database?
Greetings
Danny
> >--Original Message--
> >Hi,
> >
> >I'm a teacher in VB and use SQL 2000 on a laptop with
> Windows XP Pro.
> >My class has 20 students, can they connect to the sql
> database on my laptop?
> >
> >Thanks inadvanced.
> >
> >Danny
> >Greetings from Belgium
> >
> >
> >.
> >|||"SQLVarad" <SQLVarad@.hotmail.com> schreef in bericht
news:001601c398c3$e1c6c250$a601280a@.phx.gbl...
> Why Not?
> Scenario 1: If students want to work on SQL Server .
> You all must be within the same network/domain.
> Install SQL Server client in their PC and then configure
> the client if needed. Usually SQLServer Client identifies
> the other Servers in the same domain automatically. If the
> server is in different domain, then you have to configure
> the client(Use Named Piped Protocol/TCPIP).
> Scenario 2: Just if the students want to connect and query
> the SQL Server database from VB applications, then use
> ODBC connectivity in your application.
> Hope this helps. If not, please reply with your questions
> in detail.
> -SQLVarad (MCDBA-1999, MCSE-1999)
> Greetings from USA
>
All the students must connect to the same sql database on the laptop. The
students use ADO for the connection.
But my question was, can all the students (20) connect the same time on the
sql database.
Thanks for your answer
Greetings form Belgium
Danny
> >--Original Message--
> >Hi,
> >
> >I'm a teacher in VB and use SQL 2000 on a laptop with
> Windows XP Pro.
> >My class has 20 students, can they connect to the sql
> database on my laptop?
> >
> >Thanks inadvanced.
> >
> >Danny
> >Greetings from Belgium
> >
> >
> >.
> >|||The answer is yes...they may all connect at the same time...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Redder In Nood" <redderinnood@.hotmail-brolinpakjes.com> wrote in message
news:YAzlb.98327$FX6.4638829@.phobos.telenet-ops.be...
> "SQLVarad" <SQLVarad@.hotmail.com> schreef in bericht
> news:001601c398c3$e1c6c250$a601280a@.phx.gbl...
> > Why Not?
> >
> > Scenario 1: If students want to work on SQL Server .
> >
> > You all must be within the same network/domain.
> > Install SQL Server client in their PC and then configure
> > the client if needed. Usually SQLServer Client identifies
> > the other Servers in the same domain automatically. If the
> > server is in different domain, then you have to configure
> > the client(Use Named Piped Protocol/TCPIP).
> >
> > Scenario 2: Just if the students want to connect and query
> > the SQL Server database from VB applications, then use
> > ODBC connectivity in your application.
> >
> > Hope this helps. If not, please reply with your questions
> > in detail.
> >
> > -SQLVarad (MCDBA-1999, MCSE-1999)
> > Greetings from USA
> >
> All the students must connect to the same sql database on the laptop. The
> students use ADO for the connection.
> But my question was, can all the students (20) connect the same time on
the
> sql database.
> Thanks for your answer
> Greetings form Belgium
> Danny
> > >--Original Message--
> > >Hi,
> > >
> > >I'm a teacher in VB and use SQL 2000 on a laptop with
> > Windows XP Pro.
> > >My class has 20 students, can they connect to the sql
> > database on my laptop?
> > >
> > >Thanks inadvanced.
> > >
> > >Danny
> > >Greetings from Belgium
> > >
> > >
> > >.
> > >
>|||1. The actual number of user connections allowed also
depends on the version of SQL Server you are using and the
limits of your application(s) and hardware. SQL Server
allows a maximum of 32,767 user connections.
Because user connections is dynamic (self-configuring
option), SQL Server adjusts the maximum number of user
connections automatically as needed, up to the maximum
value allowable. For example, if only 10 users are logged
in, 10 user connection objects are allocated. In most
cases, you should not need to change the value for this
option. By default , it allows maximum users.
2. Sorry. Your questions is not clear to me. Can you
expalin in detail?
Thanks,
SQLVarad (MCDBA-1999,MCSE1999)
>--Original Message--
><anonymous@.discussions.microsoft.com> schreef in bericht
>news:02f901c398c2$79845960$a101280a@.phx.gbl...
>> Yes they can. I guess the students will be running very
>> small test queries against the sql server on your
laptop.
>Thanks for the quick answer.
>Yes, its for learning ADO
>What are the max connection for SQL server on XP Pro or
Win 2000 Pro?
>Is there a difference must I install Windows 2000 or
Windows 2003 server on
>the laptop for te connections to te SQL database?
>Greetings
>Danny
>
>> >--Original Message--
>> >Hi,
>> >
>> >I'm a teacher in VB and use SQL 2000 on a laptop with
>> Windows XP Pro.
>> >My class has 20 students, can they connect to the sql
>> database on my laptop?
>> >
>> >Thanks inadvanced.
>> >
>> >Danny
>> >Greetings from Belgium
>> >
>> >
>> >.
>> >
>
>.
>|||"Wayne Snyder" <wsnyder@.computeredservices.com> schreef in bericht
news:OgB%23MdMmDHA.2776@.tk2msftngp13.phx.gbl...
> The answer is yes...they may all connect at the same time...
>
Thanks for teh quich anwer.
Danny
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Redder In Nood" <redderinnood@.hotmail-brolinpakjes.com> wrote in message
> news:YAzlb.98327$FX6.4638829@.phobos.telenet-ops.be...
> >
> > "SQLVarad" <SQLVarad@.hotmail.com> schreef in bericht
> > news:001601c398c3$e1c6c250$a601280a@.phx.gbl...
> > > Why Not?
> > >
> > > Scenario 1: If students want to work on SQL Server .
> > >
> > > You all must be within the same network/domain.
> > > Install SQL Server client in their PC and then configure
> > > the client if needed. Usually SQLServer Client identifies
> > > the other Servers in the same domain automatically. If the
> > > server is in different domain, then you have to configure
> > > the client(Use Named Piped Protocol/TCPIP).
> > >
> > > Scenario 2: Just if the students want to connect and query
> > > the SQL Server database from VB applications, then use
> > > ODBC connectivity in your application.
> > >
> > > Hope this helps. If not, please reply with your questions
> > > in detail.
> > >
> > > -SQLVarad (MCDBA-1999, MCSE-1999)
> > > Greetings from USA
> > >
> > All the students must connect to the same sql database on the laptop.
The
> > students use ADO for the connection.
> > But my question was, can all the students (20) connect the same time on
> the
> > sql database.
> >
> > Thanks for your answer
> > Greetings form Belgium
> > Danny
> >
> > > >--Original Message--
> > > >Hi,
> > > >
> > > >I'm a teacher in VB and use SQL 2000 on a laptop with
> > > Windows XP Pro.
> > > >My class has 20 students, can they connect to the sql
> > > database on my laptop?
> > > >
> > > >Thanks inadvanced.
> > > >
> > > >Danny
> > > >Greetings from Belgium
> > > >
> > > >
> > > >.
> > > >
> >
> >
>|||Hi Wayne!
I thought that a non-server OS has connection limitations. I surely had then years ago when students
tried to run against my machine. However, this might be IPC sessions (redirector/workstation) and
only apply to Named Pipes, whereas TCP/IP Winsockets is fine...?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:OgB%23MdMmDHA.2776@.tk2msftngp13.phx.gbl...
> The answer is yes...they may all connect at the same time...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Redder In Nood" <redderinnood@.hotmail-brolinpakjes.com> wrote in message
> news:YAzlb.98327$FX6.4638829@.phobos.telenet-ops.be...
> >
> > "SQLVarad" <SQLVarad@.hotmail.com> schreef in bericht
> > news:001601c398c3$e1c6c250$a601280a@.phx.gbl...
> > > Why Not?
> > >
> > > Scenario 1: If students want to work on SQL Server .
> > >
> > > You all must be within the same network/domain.
> > > Install SQL Server client in their PC and then configure
> > > the client if needed. Usually SQLServer Client identifies
> > > the other Servers in the same domain automatically. If the
> > > server is in different domain, then you have to configure
> > > the client(Use Named Piped Protocol/TCPIP).
> > >
> > > Scenario 2: Just if the students want to connect and query
> > > the SQL Server database from VB applications, then use
> > > ODBC connectivity in your application.
> > >
> > > Hope this helps. If not, please reply with your questions
> > > in detail.
> > >
> > > -SQLVarad (MCDBA-1999, MCSE-1999)
> > > Greetings from USA
> > >
> > All the students must connect to the same sql database on the laptop. The
> > students use ADO for the connection.
> > But my question was, can all the students (20) connect the same time on
> the
> > sql database.
> >
> > Thanks for your answer
> > Greetings form Belgium
> > Danny
> >
> > > >--Original Message--
> > > >Hi,
> > > >
> > > >I'm a teacher in VB and use SQL 2000 on a laptop with
> > > Windows XP Pro.
> > > >My class has 20 students, can they connect to the sql
> > > database on my laptop?
> > > >
> > > >Thanks inadvanced.
> > > >
> > > >Danny
> > > >Greetings from Belgium
> > > >
> > > >
> > > >.
> > > >
> >
> >
>

max connections

hello everybody,
does anyone knows the max connections the sql server can work with. i need to know about the sql server capability according to hardware limits ( for exe:how many connection can the sql manege on 2 cpu's computer with 2.gb ram, etc')
thanks
Ruby
Hi
The number of connections would be limited by what you are licenced for. If
you are looking for a figure for the number of connections per second this
will mainly be limited by the capabilities of your network, although if you
expect this to be high you should probably be looking at connection pooling.
You should also look at the work carried out by each person as this will
effect the time they are connected and your hardware maybe incapable of
sustaining a reasonable level of service to the users.
For maximum capacity settings see:
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
Your hardware vendor may be able to give you some idea of what you can
expect and your should specify your requirements as part of the tender
process. This should also allow you to benchmark your application on their
hardware as part of the acceptance process.
John
"ruby" <anonymous@.discussions.microsoft.com> wrote in message
news:9245A3AA-C494-413A-A4B8-6B58C71DA9DC@.microsoft.com...
> hello everybody,
> does anyone knows the max connections the sql server can work with. i need
to know about the sql server capability according to hardware limits ( for
exe:how many connection can the sql manege on 2 cpu's computer with 2.gb
ram, etc')
> thanks
> Ruby

max connections

hello everybody,
does anyone knows the max connections the sql server can work with. i need t
o know about the sql server capability according to hardware limits ( for ex
e:how many connection can the sql manege on 2 cpu's computer with 2.gb ram,
etc')
thanks
RubyHi
The number of connections would be limited by what you are licenced for. If
you are looking for a figure for the number of connections per second this
will mainly be limited by the capabilities of your network, although if you
expect this to be high you should probably be looking at connection pooling.
You should also look at the work carried out by each person as this will
effect the time they are connected and your hardware maybe incapable of
sustaining a reasonable level of service to the users.
For maximum capacity settings see:
8dbn.asp" target="_blank">http://msdn.microsoft.com/library/d...br />
8dbn.asp
Your hardware vendor may be able to give you some idea of what you can
expect and your should specify your requirements as part of the tender
process. This should also allow you to benchmark your application on their
hardware as part of the acceptance process.
John
"ruby" <anonymous@.discussions.microsoft.com> wrote in message
news:9245A3AA-C494-413A-A4B8-6B58C71DA9DC@.microsoft.com...
> hello everybody,
> does anyone knows the max connections the sql server can work with. i need
to know about the sql server capability according to hardware limits ( for
exe:how many connection can the sql manege on 2 cpu's computer with 2.gb
ram, etc')
> thanks
> Rubysql

Max Connections

On a SQL 2005 server I have set the max user connections to 500 and
restarted the SQL Services. The server is showing this as the current
running value.
However the user connections is reporting over 30,000 and sp_who
returns over 150 with the majority of these listed as sleeping.
Why is there difference between the values returned?You are comparing the results of sp_who and what else? Where
are you getting the user connections from?
If you are using @.@.connections, that is the number of
connections and attempted connections since SQL Server
started. It will not correlated to sp_who.
-Sue
On 24 Aug 2006 06:44:11 -0700, robin9876@.hotmail.com wrote:

>On a SQL 2005 server I have set the max user connections to 500 and
>restarted the SQL Services. The server is showing this as the current
>running value.
>However the user connections is reporting over 30,000 and sp_who
>returns over 150 with the majority of these listed as sleeping.
>Why is there difference between the values returned?|||It was a MoM rule which appears to be reporting all connections and
comparing at against concurrent connections.
Sue Hoegemeier wrote:[vbcol=seagreen]
> You are comparing the results of sp_who and what else? Where
> are you getting the user connections from?
> If you are using @.@.connections, that is the number of
> connections and attempted connections since SQL Server
> started. It will not correlated to sp_who.
> -Sue
> On 24 Aug 2006 06:44:11 -0700, robin9876@.hotmail.com wrote:
>|||But that doesn't answer what it's using. I don't have MOM
running where I'm at and don't remember all the details of
what runs what but there is a way to view what it's using.
Otherwise you can use Profiler and see what MOM is executing
when it checks your SQL Server.
-Sue
On 25 Aug 2006 01:32:13 -0700, robin9876@.hotmail.com wrote:
[vbcol=seagreen]
>It was a MoM rule which appears to be reporting all connections and
>comparing at against concurrent connections.
>
>Sue Hoegemeier wrote: