Re: SqlServer *much* slower waking up than MySQL...change what configs
- From: "Roger Wolter[MSFT]" <rwolter@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Aug 2006 22:16:38 -0700
While it could be a lot of things, one obvious one is that by default SQL
Express databases are set up as auto-close which means the first connection
starts up the database. You can use ALTER DATABASE to set AUTO_CLOSE to OFF
to see if this is part of your problem.
--
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
"Sky" <public.skysigal{*AT*}xact-solutions.com> wrote in message
news:9D5D90EA-103C-4E31-B635-3F39FF0412F0@xxxxxxxxxxxxxxxx
I've installed SqlServer Express, mixed mode, on our webserver to give it
a
spin.
The first main thing that I observe is that the initial response time of
SqlServer from a PHP page is like 30 seconds to wake up and access the db.
Same operation with a MySQL is basically instantaneous: once the services
are running, the db is ready to go.
Here, it appears that SqlServer is dumping the db from memory at regular
intervals if nobody has queried for it in a while, and when it is needed
again, it takes a wildly long time to load it up, parse it, prepare
indexes,
etc.
Is there a way to configure SqlServer Express to be ready to roll
immediately? I would like to write to write an application that uses it, a
quick and dirty interface that covers a large table but with simple
requests,
and it just seems really wierd (ie wrong) that I have to write a splash
screen to cover the 10-20 seconds it takes for the db to come online.
Both MySQL as a service, and Sqlite, as an in process dll (yes, I know,
not
the same thing at all) are ready to go immediately -- I would just like to
stick with MS products if I can get around this very serious issue. Does
anybody have advice on this?
I also would like to know why in MySQL one can have several apps talking
to
the same database at the same time without locking up: ie, a DBMS, and a
website both talking to the database at the same time, same user, dif
thread.
Whereas SqlServer seems to cause an error if I open the same db with the
DBMS, or Visual Studio, and then try to run the website, or vice versa,
with
the same credential.
This just has to be from a misunderstanding on my part of how to set up
and
use SqlServer. Any advice for this?
.
- Follow-Ups:
- Prev by Date: Re: Let me rephrase: Connection Timeouts on local machine ?
- Next by Date: Re: Let me rephrase: Connection Timeouts on local machine ?
- Previous by thread: Re: Let me rephrase: Connection Timeouts on local machine ?
- Next by thread: Re: SqlServer *much* slower waking up than MySQL...change what con
- Index(es):
Relevant Pages
|
