"Farzana" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> The query we used is "SELECT * FROM Brand ORDER BY BrandDescription".
> The Brand table contains more than 30,000 records. The execution time
> is reasonable when we execute in the system.But it is slower when we
> execute the
The query we used is "SELECT * FROM Brand ORDER BY BrandDescription". The
Brand table contains more than 30,000 records. The execution time is
reasonable when we execute in the system.But it is slower when we execute
the same in the device.
Regards,
Farzana.
Igor Tandetnik wrote:
>
>
CREATE INDEX BrandKey2 ON Brand(BrandDescription);
On Wed, May 14, 2008 at 7:32 AM, Farzana <[EMAIL PROTECTED]> wrote:
>
> Thanks for your reply Igor.
>
> When we checked with the provided query we found that the duplicate values
> are present in the BrandDescription. We are working with the
Thanks for your reply Igor.
When we checked with the provided query we found that the duplicate values
are present in the BrandDescription. We are working with the device where
the memory is limited. We are suppose to sort the data by
BrandDescription.When we tried with "ORDER BY
"Farzana" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> We are using SQLite and we have the table structure as CREATE TABLE
> Brand(PcNo numeric(4) Not Null,SubPcNo numeric(4) Not Null,BrandNo
> numeric(9) Not Null,BrandDescription nVARCHAR(254)Not Null,ST
> numeric(1),TS
Dear All,
We are using SQLite and we have the table structure as CREATE TABLE
Brand(PcNo numeric(4) Not Null,SubPcNo numeric(4) Not Null,BrandNo
numeric(9) Not Null,BrandDescription nVARCHAR(254)Not Null,ST numeric(1),TS
numeric(14)) where the index is CREATE UNIQUE index BrandKey1 on
6 matches
Mail list logo