From: "Robert Comer" 

>A lot
> of the time there isn't even an index so they can run for a bit.

Build 'em to fit your normal query patterns, it'll save you time in the long run.

> All I really need is a way to do one of these queries so that it runs at a
> low priority and doesn't slow down the other processes running. It's not
> that I have to wait for the query to complete, I've got all day, it's that
I
> don't want to bog the system just because I asked sql server for something
> unusual.

Building indexes will help in this regard too by not sucking up resources
for ad hoc queries.

- Bob Comer


"Geo."  wrote in message
news:3e0fae99$1{at}w3.nls.net...
> "Ellen K."  wrote in message
> news:du0v0vs95nqj79bchah299bgkmj0dfdfp6{at}4ax.com...
>
> > I just thought of something... if you have a lot of queries that make
> > use of nonclustered indexes, you could probably improve performance
> > significantly by putting the nonclustered indexes on their own disk or
> > set of disks.
>
> The common queries are fast, the database was designed by a guy who I
> consider to be a real expert with sqlserver. The problem comes in when I
> have to do ad hoc queries looking for something or checking something. A
lot
> of the time there isn't even an index so they can run for a bit.
>
> All I really need is a way to do one of these queries so that it runs at a
> low priority and doesn't slow down the other processes running. It's not
> that I have to wait for the query to complete, I've got all day, it's that
I
> don't want to bog the system just because I asked sql server for something
> unusual.
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-4