Re: Number of allowed connections for SQL Server 2005 Standard on

Tech-Archive recommends: Fix windows errors by optimizing your registry

The other thing to keep in mind is that regardless of any SQL Server limitations, Windows XP only has 10 TCP/IP connections so supporting 30 concurrent users might not be possible. XP is tuned to give preference to UI foreground application and not IO and memory intensive applications like SQL Server so performance often isn't what you expect.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"michael" <michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:212C8757-2AE9-4D70-B57C-986F384BB85C@xxxxxxxxxxxxxxxx
I did think about this for a bit, so, my answer will probably expose some of
my ignorance on the subject. My apologies in advance.

The reason I want to use XP Pro is that I already own a copy running on a
spare machine. The machine belongs to a domain managed on another box.
Nothing else running on the XP box. Nothing about the operation of the
database is really mission critical. I may have 10 - 30 concurrent users,
but, that's about it. I can put as much memory and storage space as I want.

What would I really get by running SQL Server 2005 on an MS server platform
in such a situation?

Respectfully,



--
Michael


"William (Bill) Vaughn" wrote:

Yup... and the amount of CPU time you can dedicate to the threads SQL Server
will generate to handle the operations.
Let's hear more about your connection strategy and application architecture.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:OSgPZMRiHHA.4596@xxxxxxxxxxxxxxxxxxxxxxx
>I believe that is a wrong assumption. There is no limit based on the OS
>that I know of other than the fact that 64 bit can support more memory >for
>connections. But if you are worried about lots of connections then why
>would you want to use XP Pro? The # of connections will ultimately be
>limited by the amount of memory and the hardware.
>
> -- > Andrew J. Kelly SQL MVP
>
> "michael" <michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0EA3B57E-6583-4A59-B38B-FB4C89AB5D74@xxxxxxxxxxxxxxxx
>>I assume that the number of connections that SQL Server 2005 Standard >>can
>> concurrently have will be limited by the operating system it is >> running
>> on.
>> If that OS is XP Pro, how many concurrent connections can SQL Server >> 2005
>> Standard have?
>>
>> -- >> Michael
>
>




.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • RE: Memory issue using OleDbConnection with SQL Server
    ... > First of all, I'm not quite sure if this is the right place asking this> question, it may very well be a SQL Server issue, but I'll start here. ... > For normal operation and load, it seems to do OK, but when I do a lot of> database calls during a> short period of time, the server memory literally goes through the roof. ... > - I thought it might have something to do with the database connections> being left open in a pool, but the high memory use remains even after the> application is stopped. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)