indexs, primary and such

[entoone]

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds
for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response times. I
think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field with
a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds
for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response times. I think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field with a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds
for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response times. I think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field with a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds
for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response times. I think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field with a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[entoone]

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response

times. I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[entoone]

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response

times. I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[entoone]

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3 seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.

I'm looking for the best way to create my indexes for fast response

times. I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToonE -
great - did you see any performance change ???
lemme know [though its hard for 200 records to time it accurately]
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:m1**********************@newssvr13.news.prodi gy.com...

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via

email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3

seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.
I'm looking for the best way to create my indexes for fast response

times.

I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToonE -
great - did you see any performance change ???
lemme know [though its hard for 200 records to time it accurately]
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:m1**********************@newssvr13.news.prodi gy.com...

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via

email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3

seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.
I'm looking for the best way to create my indexes for fast response

times.

I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!

[swdev1]

EnToonE -
great - did you see any performance change ???
lemme know [though its hard for 200 records to time it accurately]
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:m1**********************@newssvr13.news.prodi gy.com...

Thanks much for the post. I heard ya, and have done that. Thanks!
"swdev1" <ws**********@advmed.com> wrote in message
news:Ng****************@newssvr24.news.prodigy.com ...

EnToone -
basically any column that I would use as part of the record selection
criteria -
i.e. WHERE clauses
JOIN criteria
would be a good column to index on. So map out what you want to do, on
paper, with your select statements and study your where clauses and join
criteria - then index those columns.

let me know how it goes for you .
mondo regards [Bill]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via

email.
FREE LONG DISTANCE -> mailto:ex********@efgroup.net
mySql / VFP / MS-SQL
"entoone" <en*****@pacbell.net> wrote in message
news:BM******************@newssvr21.news.prodigy.c om...

I have a very small db of only like 15 files, and with 120 records.

If I do a query from the page, via a php file it seems to take 2-3

seconds for the results to come up.
I'm anticipating having a lot more records, upwards of 300-800 records.
I'm looking for the best way to create my indexes for fast response

times.

I

think right now that the performance isn't that slow.

My primate key is presently set to ID which is an autoincremting field

with

a length of 6.

I do have queries that call for records that match a state also.

Any suggestions? thanks for your time!