Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
SQL
ce
clients
clustering
connect
datamining
datawarehouse
dts
fulltext
jdbcdriver
msde
mseq
newusers
notificationsvcs
odbc
olap
programming
replication
reportingsvcs
security
securitytools
server
setup
sqlxml.viewmapper
tools
xml
  
 
date: Wed, 26 Apr 2006 09:34:46 -0400,    group: microsoft.public.sqlserver.newusers        back       


SQL Server Express limitations   
My boss is trying to answer the question: Is there a limit to the number 
of concurrent "users" in SQL Server Express 2005 ?

I realize the hardware limitations of SSE (1GB ram, 1 processor, 4GB 
database size) but management unearthed a document from 11/05 from 
Microsoft that seemed to indicate that there was a limit on the number 
of concurrent users and since we are certified partners they called an 
MS representative who declined to guarantee that there was no limit.

I personally think that concurrent 'connections' would be a better way 
to ask the question, but this is a difficult distinction to explain to 
the golfing echelon.

Can anyone help with this ?

Thank you
Dave Joyner
date: Wed, 26 Apr 2006 09:34:46 -0400   author:   Dave Joyner

Re: SQL Server Express limitations   
No there isn“t and there has never been, the query governour (if you
mean that by concurrent users) is sent into retirement.

HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---
date: 26 Apr 2006 07:28:39 -0700   author:   Jens

Re: SQL Server Express limitations   
MSDE 1.0 and MSDE 2000 contained a workload governor that limited 
performance when the number of concurrent workloads (operations) reached a 
set limit. The workload governor was discontinued and is not part of SQL 
Server 2005 Express Edition. That is documented in the Express Edition Books 
Online:

http://msdn2.microsoft.com/en-us/library/ms165672(SQL.90).aspx

One of the reasons the workload governor was discontinued is that it proved 
difficult to explain to computer science majors, much less the golfing 
echelon. The trigger point really depended on the number of concurrent 
operations acctive in the database engine, which does not relate back to the 
number of concurrent connections or users. Early explanations of the 
governor tried to discuss it in terms of connections or users, but that was 
confusing to customers because some systems would have the governor kick in 
with 10 connections, while others could have 100 relatively inactive 
connections and never hit the limit.

In case you're interested, a more in-depth discussion of the workload 
governor can be found at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp

Also note that SQL Server 2005 does have a query cost governor that people 
can confuse with the discontinued workload governor. The query cost governor 
is a configurable option for stopping resource-intenstive queries:
http://msdn2.microsoft.com/en-us/library/ms176100(SQL.90).aspx

-- 
Alan Brewer [MSFT]
Content Architect, SQL Server Documentation Team

SQL Server Developer Center: http://msdn.microsoft.com/sql
SQL Server TechCenter: http://technet.microsoft.com/sql/

This posting is provided "AS IS" with no warranties, and confers no rights.
date: Wed, 26 Apr 2006 12:02:02 -0700   author:   Alan Brewer [MSFT]

Re: SQL Server Express limitations   
http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx

"Dave Joyner"  wrote in message 
news:uAgKwYTaGHA.4564@TK2MSFTNGP03.phx.gbl...
> My boss is trying to answer the question: Is there a limit to the number 
> of concurrent "users" in SQL Server Express 2005 ?
>
> I realize the hardware limitations of SSE (1GB ram, 1 processor, 4GB 
> database size) but management unearthed a document from 11/05 from 
> Microsoft that seemed to indicate that there was a limit on the number of 
> concurrent users and since we are certified partners they called an MS 
> representative who declined to guarantee that there was no limit.
>
> I personally think that concurrent 'connections' would be a better way to 
> ask the question, but this is a difficult distinction to explain to the 
> golfing echelon.
>
> Can anyone help with this ?
>
> Thank you
> Dave Joyner
date: Thu, 27 Apr 2006 13:24:00 -0700   author:   Euan Garden

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us