Re: Memory usage\Performance problem
- From: "Robert Klemme" <bob.news@xxxxxxx>
- Date: Mon, 29 Aug 2005 16:28:19 +0200
Magnus Österberg wrote:
> I guess my expectations on selecting based on a non-indexed column
> were somewhat high. When I added an index, my query executes in
> seconds.
> One index solved this problem, but my table contains 30-40 similar
> columns, and I don't think indexing every column is a good idea.
Two things come to mind:
1. rethink your table design. If these columns are so similar you might
be better off with a second table which is joined. But that of course
depends on your data - just an idea.
2. Create indexes (possibly composite indexes) for most used queries. You
might even get away with a single (or few) composite index if your queries
only use a leading portion of this index's fields.
> Isn't there any other ways of speeding up selects? Well, I guess
> not...
Well, there are tons of other options, like having data files on several
disks, putting tx log on a separate disk, adding memory, .... It all
depends. :-)
Kind regards
robert
.
- Follow-Ups:
- Re: Memory usage\Performance problem
- From: Magnus Österberg
- Re: Memory usage\Performance problem
- References:
- Memory usage\Performance problem
- From: Magnus Österberg
- Re: Memory usage\Performance problem
- From: Erland Sommarskog
- Re: Memory usage\Performance problem
- From: Magnus Österberg
- Memory usage\Performance problem
- Prev by Date: SET IMPLICIT_TRANSACTIONS ON
- Next by Date: Rewrite a WHERE clause
- Previous by thread: Re: Memory usage\Performance problem
- Next by thread: Re: Memory usage\Performance problem
- Index(es):