Thanks. I'll give that a try...
On Sat, Oct 1, 2011 at 2:35 AM, Jochem van Dieten wrote:
>
> On Fri, Sep 30, 2011 at 11:45 PM, John M Bliss wrote:
> > type 1 - about 1-5 SELECTS per second that have to run as fast as
> possible
> > *always* (< 1 second)
>
> > My question is: if the goal is to m
On Fri, Sep 30, 2011 at 11:45 PM, John M Bliss wrote:
> type 1 - about 1-5 SELECTS per second that have to run as fast as possible
> *always* (< 1 second)
> My question is: if the goal is to make sure type 1 remains as fast as
> possible, will it help/hurt to also declare "SET TRANSACTION ISOLATI
I recommend doing this as an optimization technique, as long as you
are aware of the tradeoff you are making. The default database
settings are optimized for ACID transactional safety, but most Web
sites don't need this level of safety unless you are handing financial
transactions. Most of the NoS
We have a fairly high-traffic ACF 8 site where SQL Server database gets hit
with two types of queries:
type 1 - about 1-5 SELECTS per second that have to run as fast as possible
*always* (< 1 second)
type 2 - about 100-500 "other" queries per day that are allowed to run
"slower" (5-20 seconds). (
4 matches
Mail list logo
