Hi,
If SQL Server 2005 Express is running on Windows XP Home, it is limited to
five simultaneous connections. If it is running on Windows 2000 or Windows XP
Professional, it is limited to 10 simultaneous connections. However, these
are limitations of the operating system and not of SQL Server 2005 Express

Where are the setting of this ? can we modify this ?

TIA,
Kishor

Where have you found these limitation?
If found by test, have you only uses NAMED PIPES? Or have you tried TCP
connection too?

"kishor" <kishor (AT) discussions (DOT) microsoft.com> a écrit dans le message de
news:55CBB500-1C29-47BF-A2B1-4CEEF36031EE (AT) microsoft (DOT) com...

I don't believe Win2000 is limited to 10 connections since it is a server OS
vs. the workstations ones like XP. AFAIK you can not change these limits.
If you need more than 10 simultaneous connections you should be running a
server OS and SQL Express is probably not the correct edition either.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"kishor" <kishor (AT) discussions (DOT) microsoft.com> wrote

Yes thats true; SQL Express is not a right version and XP is also not a
Server operating system. but how come these limits are very small ?

Regards,
kishor

"Andrew J. Kelly" wrote:

Hi,
I was just going through this page

http://www.microsoft.com/technet/pro...qlexpress.mspx

I found this.

Regards,
kishor


"Pascal Deliot" wrote:

They are small because of the fact that the OS is not optimized for that
type of work and it they allowed more connections you wouldn't have to pay
more for the server version.


--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"kishor" <kishor (AT) discussions (DOT) microsoft.com> wrote

I asked you this cause this kind of limitation is easy to understand with
NAMED PIPE cause this is linked to OS.
But I'm not sure this limit apply to TCP connections.

"kishor" <kishor (AT) discussions (DOT) microsoft.com> a écrit dans le message de
news:820984B0-01A3-4FF6-AC79-4653400F3D5D (AT) microsoft (DOT) com...

The 10-connection limit is an arbitrary limit enforced by Microsoft for the
non-server OS. The OS controls TCP connections too, the same as named pipes.
You may find hacks to get around the limit, but there isn't any legitimate
way to bypass the connection limit. It's also a restriction specified in the
OS license.

"Pascal Deliot" <PDELIOT (AT) microsoft (DOT) com> wrote