Concurrent queries exceeded

I am getting the following error message on a test SQL
Server:
'This SQL Server has been optimized for 8 concurrent
queries. This limit has been exceeded by 7 queries and
performance may be adversely affected.'
However, I can't seem to find any reference to this
anywhere let alone how to actually change the number of
concurrent queries!
Has anybody else had this problem or know's how to chnage
the setting?
Cheers
Lee.Looks like you are running MSDE. MSDE is optimized for 5 client and 3 server
process concurrent queries.
MSDE is free but is governed to limit performance.
If you need more concurrent connections and queries, you need to install a
full version of SQL Server.
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Lee Pantling" <Lee.Pantling@.SGP.co.uk> wrote in message
news:054f01c3d9e4$83b146b0$a001280a@.phx.gbl...

quote:

---

> I am getting the following error message on a test SQL
> Server:
> 'This SQL Server has been optimized for 8 concurrent
> queries. This limit has been exceeded by 7 queries and
> performance may be adversely affected.'
> However, I can't seem to find any reference to this
> anywhere let alone how to actually change the number of
> concurrent queries!
> Has anybody else had this problem or know's how to chnage
> the setting?
> Cheers
> Lee.

---

|||This is generated by the workload governor that is in SQL Server 2000
Personal Edition and SQL Server 2000 Desktop Engine (MSDE 2000). Information
about the governor is at this Web page:
http://www.microsoft.com/sql/msde/t...workloadgov.asp
You cannot change the setting of the workload governor. If it is limiting
the performance of your instance of SQL Server, you would have to upgrade to
SQL Server 2000 Standard Edition or Enterprise Edition to get a version of
SQL Server that does not have the governor. If the governor is not getting
invoked often, it may not have much of an effect on the performance of your
systsem.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights