Re: vb.net/sql server speed issue

From: Joe Fallon (jfallon1_at_nospamtwcny.rr.com)
Date: 04/12/04 

Date: Sun, 11 Apr 2004 23:16:49 -0400

That is the right design.
But that doesn't mean you aren't running into the governor.
A lot depends on how the app is used.
Many apps, the user spends a lot of time reading screens.
If in your app they are "always" fetching data then the governor could kick
in.

Did you try running DBCC CONCURRENCYVIOLATION to see the output? 

-- 
Joe Fallon
"Chandler Dickinson" <hunter-mail@mindspring.com> wrote in message
news:OZ3eF4zHEHA.2720@TK2MSFTNGP11.phx.gbl...
> Well this is my concern and that of my client... it is assumed that the
> application was not designed well... but i can't imagine anything i did
> wrong... i have a external dll containing all my data calls using the
> dataadapter hit the database build a dataset and drop the connection....
> return the dataset to the calling proceedure and that's that... this does
> not seem wrong does it... your help is appreciated...
>
> Chandler
> "Joe Fallon" <jfallon1@nospamtwcny.rr.com> wrote in message
> news:enkvaczHEHA.2756@TK2MSFTNGP10.phx.gbl...
> > MSDE is the same engine as SQL Server but it has 2 major limitations.
> > Looks like you are running into #2 below.
> >
> > 1. The max DB size is 2GB.
> >
> > 2. There is a "governor" in place that throttles back performance when
> more
> > than 5 concurrent processes are running.
> >
> > MS recommends that you use a full version of SQL Server to develop your
> > database on.
> > You really need all of the tools available like QA and EM, etc.
> >
> > The idea would be for you to install MSDE for free at the client site
and
> > the restore your database to it (or build it from scratch using commands
> > that can be genearted from EM.)
> >
> > MSDE is the SQL Server engine with a couple of limitations like 2 GB of
> data
> > and 5 concurrent *processes* (that is not the same thing as users.) Over
5
> > processes, and the throttle kicks in to slow things down. There is a
> command
> > in MSDE (DBCC CONCURRENCYVIOLATION) which shows how many times the
> throttle
> > has kicked in. You are supposed to run it weekly or monthly and see if
it
> is
> > time to upgrade to a full version of SQL Server. (BTW, a well designed
app
> > should run so fast that you might be able to support 50-100 simultaneous
> > users without bumping into the throttle.)
> > --
> > Joe Fallon
> >
> >
> >
> >
> > "Chandler Dickinson" <hunter-mail@mindspring.com> wrote in message
> > news:unSVXFvHEHA.3248@TK2MSFTNGP12.phx.gbl...
> > > I have a vb.net application running with sql server...  All calls to
the
> > > database are hit and drop.... i keep no connections open.... there are
> two
> > > timers in the application that hit the database to check for
new/changed
> > > information (small hits)... here is the problem...
> > >
> > > this one has be whipped... please help if you can...
> > >
> > > I have only about 80 to 100 users peak... on mondays and fridays my
> users
> > > are less and the application runs fine but tuesday-thursday my app
will
> > run
> > > fast as lightning unit about 10:00am when the user counts go from
50-60
> to
> > > 80-100 and then BAM  the entire application on all clients machines
come
> > to
> > > a screeching halt... and will remain that way until a few (5-7) users
> exit
> > > the application.... then the speed will go back to light speed...
> Also...
> > > it appears that on the first day after putting the database on a new
> > server
> > > it screams regardless of the number of users... but on day 2 the
problem
> > > comes back... I have actually had this thing running in the past on a
> MSDE
> > > sql server with the same results... DB, Connections, my App?????? What
> the
> > > heck is going on help help help...
> > > Chandler Dickinson
> > >
> > >
> >
> >
>
>