yl" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, October 26, 2004 7:26 PM
Subject: Re: question about indexes
See responses embedded
"DeRyl" <[EMAIL PROTECTED]> wrote on 10/26/2004 12:58:38 PM:
> hi again,
>
> I always must search with
t;
> regards
> DeRyl
>
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: "DeRyl" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, October 26, 2004 6:17 PM
> Subject: Re: question about indexes
&
Sent: Tuesday, October 26, 2004 6:17 PM
Subject: Re: question about indexes
You asked about indexes for these tables
I would make "dictionaryid" the PK of each dictionary_tbl.
I would add an index to each dictionary_tbl for dictionaryword.
I would make the PK for dict_client_tbl (clie
You asked about indexes for these tables
I would make "dictionaryid" the PK of each dictionary_tbl.
I would add an index to each dictionary_tbl for dictionaryword.
I would make the PK for dict_client_tbl (clientid, dictionaryid)
You also asked about fastest possible searches.
Whenever you hav
hello,
I have a main table called client_tbl which contains:
clientid bigint(14) [primary key]
zoneid smallint(2) [secondary key]
clientame varchar(255)
clientaddress
clientemail
clientwww
clientinfo
clientamount decimal(6,1)
and a lot of dictionaries that are int he same schema - so I describe
I seem to remember that Microsoft SQL Server has the concept of a "covered index" that
worked something like this:
Suppose you have a table with a product_category, and a price. You query alot on
product_category, so you create an index on it. You're expression might look like
this:
select
