MSDE Performance Governor - knowing when its kicked in

I'm working on a VB.NET project where we are intending to use MSDE as our
back-end database. The actual number of users is expected to be low and I
don't have any concerns as to whether MSDE will be up to the job (most of
the time). I'm aware that if we end up with lots of users connecting to our
site at once (which may happen as certain times in the year when people need
information for deadlines) then the performance governor in MSDE will kick
in and slow everything down.

What I don't know is how do I find out whether the performance governor has
kicked in?

I would like to know how to monitor this so we can make an educated decision
as to when we need to migrate to a full version of SQL Server (if at all).

Can anyone point me in the right direction for finding this out?

thanks,

Brian Cryer."Brian Cryer" <brianc@.127.0.0.1.activesol.co.uk> wrote in message
news:1106559318.8377.0@.damia.uk.clara.net...
> I'm working on a VB.NET project where we are intending to use MSDE as our
> back-end database. The actual number of users is expected to be low and I
> don't have any concerns as to whether MSDE will be up to the job (most of
> the time). I'm aware that if we end up with lots of users connecting to
> our
> site at once (which may happen as certain times in the year when people
> need
> information for deadlines) then the performance governor in MSDE will kick
> in and slow everything down.
> What I don't know is how do I find out whether the performance governor
> has
> kicked in?
> I would like to know how to monitor this so we can make an educated
> decision
> as to when we need to migrate to a full version of SQL Server (if at all).
> Can anyone point me in the right direction for finding this out?
> thanks,
> Brian Cryer.

Check out DBCC CONCURRENCYVIOLATION in Books Online. If you don't already
have the latest version of BOL, then you should download it, as it has more
detailed information about MSDE and the workload governor that wasn't in
previous versions.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:41f4c703$1_1@.news.bluewin.ch...
> "Brian Cryer" <brianc@.127.0.0.1.activesol.co.uk> wrote in message
> news:1106559318.8377.0@.damia.uk.clara.net...
> > I'm working on a VB.NET project where we are intending to use MSDE as
our
> > back-end database. The actual number of users is expected to be low and
I
> > don't have any concerns as to whether MSDE will be up to the job (most
of
> > the time). I'm aware that if we end up with lots of users connecting to
> > our
> > site at once (which may happen as certain times in the year when people
> > need
> > information for deadlines) then the performance governor in MSDE will
kick
> > in and slow everything down.
> > What I don't know is how do I find out whether the performance governor
> > has
> > kicked in?
> > I would like to know how to monitor this so we can make an educated
> > decision
> > as to when we need to migrate to a full version of SQL Server (if at
all).
> > Can anyone point me in the right direction for finding this out?
> > thanks,
> > Brian Cryer.
> Check out DBCC CONCURRENCYVIOLATION in Books Online. If you don't already
> have the latest version of BOL, then you should download it, as it has
more
> detailed information about MSDE and the workload governor that wasn't in
> previous versions.
> Simon

Excellent Simon. Just what I was after.

Many Thanks.

Brian.

MSDE Limits and users....SQL2005

Hi,
I have read the paperwork on MSDE, it's limits, governor, etc., and I am
wondering for a real-world perspective if 25 - 30 users is fine or if it we
would experience problems using this? With SQL2005 just around the corner I
don't want to have my client order SQL2000 and then be told they need to
upgrade X months down the road.
Thanks,
Chris
hi Chris,
Chris Marsh wrote:
> Hi,
> I have read the paperwork on MSDE, it's limits, governor, etc., and I
> am wondering for a real-world perspective if 25 - 30 users is fine or
> if it we would experience problems using this? With SQL2005 just
> around the corner I don't want to have my client order SQL2000 and
> then be told they need to upgrade X months down the road.
you actually have to test your scenario... it really depends on code
standards, data load, hardware, but application rules too...
by the way, SQL Express will not have the Query Governor, but other kind of
limits, such as only 1 cpu (MSDE 2000 allows 2), and 1 GB ram (MSDE 2000
allows 2) use, so my understanding is that things will not change
drammatically with the new product...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you! Unfortunately, I cannot test 30 users in my own office (just not
that big) so the only option is to try live at a client site. If this would
fail, what would I expect just slower performance?
Also, if you are saying that Express and MSDE will have similiar performance
results due to different crippling approaches then if I have my app running
in an enviornment where it's already a single processor and 1GB RAM and it's
running fine there then this might be a mute point - correct?
Again thanks
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3f1t3jF5iiqrU1@.individual.net...
> hi Chris,
> Chris Marsh wrote:
> you actually have to test your scenario... it really depends on code
> standards, data load, hardware, but application rules too...
> by the way, SQL Express will not have the Query Governor, but other kind
> of limits, such as only 1 cpu (MSDE 2000 allows 2), and 1 GB ram (MSDE
> 2000 allows 2) use, so my understanding is that things will not change
> drammatically with the new product...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Chris,
Chris Marsh wrote:
> Thank you! Unfortunately, I cannot test 30 users in my own office
> (just not that big)
:D

>so the only option is to try live at a client
> site. If this would fail, what would I expect just slower
> performance?
you should check for time out problems too in your application code... as
you already know, when the Governor kicks in, all active batches are slowed
down, with performance "problems" (:D) ...

> Also, if you are saying that Express and MSDE will have similiar
> performance results due to different crippling approaches then if I
> have my app running in an enviornment where it's already a single
> processor and 1GB RAM and it's running fine there then this might be
> a mute point - correct?
did not made actual performance tests, and SQL Express is till in beta, but
I think the 2 environments, from a performance point of view, should be
pretty similar... but, all this, IMHO..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks - guess it's just a game of guessing
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3f3qcuF5q44jU1@.individual.net...
> hi Chris,
> Chris Marsh wrote:
> :D
>
> you should check for time out problems too in your application code... as
> you already know, when the Governor kicks in, all active batches are
> slowed down, with performance "problems" (:D) ...
>
> did not made actual performance tests, and SQL Express is till in beta,
> but I think the 2 environments, from a performance point of view, should
> be pretty similar... but, all this, IMHO..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>