asked on
Optimizing a Simple Select
I have a very simple select statement:
It's running on a table that has 36 Million records. I'd like to it be faster.
I have two indexes setup, one on stat_account and one on stat_created.
So first of all, is there something I should do to make the query faster? Like maybe COUNT(*) isn't a good idea, or there something better than BETWEEN?
And secondly, should I change my indexes? Make a combo index that includes account and created?
Or maybe you have another idea?
Thank you!
SELECT COUNT(*) as varTotal
FROM tbl_stat_master
WHERE stat_account = 173
AND stat_created
BETWEEN '2012-11-01 00:00:00'
AND '2012-12-01 00:00:00'
It's running on a table that has 36 Million records. I'd like to it be faster.
I have two indexes setup, one on stat_account and one on stat_created.
So first of all, is there something I should do to make the query faster? Like maybe COUNT(*) isn't a good idea, or there something better than BETWEEN?
And secondly, should I change my indexes? Make a combo index that includes account and created?
Or maybe you have another idea?
Thank you!
DatabasesMySQL ServerSQL
Last Comment
Ryan
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
To clarify a few things:
We never do deletes.
We insert about 1000/records per minute during peak times and average about 100/minute over all.
We're considering purging old data (might be a good separate question on the most efficient way to delete records older than x days on a regular basis).
A few questions...
To type cast, is this the best way:
Open in new window
Also, if I transform the dates to integers for existing and new incoming records, what would be the best way to do: '2012-11-01 12:59:02'
I'm assuming since I only want month granularity I can just use:
201211
And put an index on that column? That seems to me like it would probably lead to a big performance boost.
@MrBullwinkle-- you said "I think the engine can optimize the repeat calls if you use @parameters rather than a string literal". I'm not sure what @parameters are?
Thanks again for all your help!