> > Got me again dang nabit!
>
> You turning Texan on us mate? <bg>

Nah - just been watching too much of those old Warner Bro's cartoons lately.

> << Of course, queries with joins can't be returned as a live result set,
so
> I'm assuming that this particular query will normally take 1.25 seconds to
> complete, to return the 4200 odd records, so in effect, maybe the queries
> not slow at all, and it's moreso the other way around, that the live
result
> set setting is quick.  >>
>
> Bingo !  Couldn't have said it better myself.  It's very much like the
> OpLocks issue - the issue is not that having multiple users is
particularly
> slow, it's that having a single user is particularly fast.  There's a
> certain overhead to creating the result set and populating it for canned
> result sets.

Tim, It's Funny you mention oplocks. Just this morning, I received
information from one of those clients where the IT Administrator nuked the
backup schedules, and recreated them. In doing so, he's free'd up
"something", and now the system works just as fast on 2003 as it used to
when a Windows XP workstation was operating as a file server - with multiple
users and all.

I'm guessing that in this instance, oplocks weren't an issue, and there must
have been something else causing issues. They've still got no idea what
exactily they've done though, as it would be handy to know.

Cheers

Adam.

There is a principle which is a bar against all information, which cannot
fail to keep a man in everlasting ignorance-- that principle is contempt
prior to investigation." - Herbert Spencer, British philosopher.

Adam,

<< Tim, It's Funny you mention oplocks. Just this morning, I received
information from one of those clients where the IT Administrator nuked the
backup schedules, and recreated them. In doing so, he's free'd up
"something", and now the system works just as fast on 2003 as it used to
when a Windows XP workstation was operating as a file server - with multiple
users and all.

I'm guessing that in this instance, oplocks weren't an issue, and there
must have been something else causing issues. They've still got no idea what
exactily they've done though, as it would be handy to know. >>

My guess is something like "hot backup" or similar was disabled.  Usually
these types of slowdowns are due to mirroring, indexing, or some other file
system function that you aren't aware of being enabled.

--
Tim Young
Elevate Software
www.elevatesoft.com